Turn a customer enquiry into an accountable next action

A concrete workflow for combining inbox context, CRM follow-up and verification without inventing customer commitments.

Define the useful result

A customer enquiry often starts in email or chat and finishes somewhere else: a CRM task, a draft reply, a booking or a handoff to another person. The difficult part is keeping the context and the next action together. An AI teammate can help, but the workflow should make its result observable.

Start by describing what you actually want. “Read this enquiry and draft a reply with the agreed next step” is a bounded task. “Send the approved reply and log the follow-up” is a different task with an external action. A good assistant should follow the authority you gave, without assuming more or repeatedly asking for the same approval.

Read the relationship before drafting

First identify the intended person and organisation. A stable email or record link is more reliable than a display name alone. Read the relevant thread and recent activity, including any open task or recent send that could make another follow-up a duplicate.

The assistant should distinguish a customer’s question, a colleague’s suggestion and an actual commitment. If a price, deadline or availability claim could have changed, use its current authoritative source. Do not fill a gap with plausible-sounding detail.

Choose the next step deliberately

A useful next step has an action and an owner. It might be answering an open question, preparing a proposal, requesting missing information or offering an existing booking link. A note saying “follow up later” is less useful when nobody can tell who should do it or when.

Avoid inventing a meeting slot. Use verified availability or the intended booking page. If the customer has not accepted a proposal or confirmed a time, record that uncertainty rather than moving a deal to a stage that implies more progress than occurred.

Check the account and the tools

In Cortex Chat, the visible email surface and the Sidekick’s Email permissions are separate. The active mailbox matters, as do the saved read, draft or send allowance and the individual tools. A private assistant context can also differ from a shared group context.

Inspect the actual connection and policy before concluding that an assistant can act. If the task only needs a draft, there is no need to enable sending just to make the workflow appear more complete.

Verify the destination

After an authorised send, inspect the sent item or supported send result. After creating a task, check its owner, date and contact. After a booking, inspect its confirmed event and invitation. A confident summary is useful communication, but it is not the destination evidence.

If a request times out, reconcile the existing result before retrying. This prevents a technical uncertainty from turning into duplicate customer contact. The final handoff should say what was drafted, saved or sent and identify any remaining decision.

Make the method reusable

The Fulcrum CRM follow-up skill captures this procedure in a readable file. It is one of the public starter skills, alongside data-quality review, inbox triage, booking setup and meeting actions. These procedures help the team repeat a useful method; they do not grant access to a customer database on installation.

Begin with a small real task you are authorised to perform, compare the result with the source material and refine the procedure when a concrete failure shows what is missing.

Read the practical references

Also published on LinkedIn.