Chatbot information versus action separates an explanation of a process from an actual change in its system. “You can cancel the appointment” describes a possibility, “we received the request” describes receipt, and “the appointment is cancelled” requires evidence of execution. Do not use those sentences interchangeably. Identify the source of truth and status messages for one process so that customers do not wait for an action that was never started or completed.
Establish whether the customer wants an explanation or a change
A question about whether an action is possible is not always an instruction to perform it. “Can I change the date?” may be checking conditions before a decision, whereas “change it to Friday” expresses a specific request. Read the words without adding intention and clarify a missing detail when necessary. Treating every conversation about change as permission to save it creates an execution message for an operation the customer may not yet have decided to request. For a tradesperson this is often "can you come on Thursday?", and the assistant should not confirm a date but refer the request to a person, as the guide to an AI assistant for trades businesses explains.
Conversely, do not provide only instructions when the customer explicitly expects the team to act. Name the status: “I can explain the steps but do not make that change in this conversation”, or “the request is awaiting confirmation”. Broader roles belong to AI in customer support. Here you are designing the meaning of one message rather than selecting an assistant mode, ensuring that an explanation of capability does not resemble evidence of a completed operation.
Identify the system that confirms the actual change
The source of truth is the record in the system responsible for the action, not the sentence in the conversation. For a booking, inspect its current calendar state; for a document, check the issue reference; for a data change, read the updated record. Sending a request alone does not prove that the change was accepted. Choose evidence available to the operator and specify what should change after successful execution before you prepare a confirmation template.
Customers do not need your internal system names. A understandable result, such as the new date in their current booking details, is sufficient. Booking cancellation rules are separate; this example concerns cancellation evidence rather than date selection. A button click is not final evidence if it can be followed by an error, permission refusal or a wait for the process owner's decision, so review the recorded state before describing the result as finished.
Write different messages for three states
Messages should distinguish information, pending work and completion even when they appear in the same thread. For information, give the instruction and say the existing state remains. For pending work, name the received request, unconfirmed part and possible next step. For completion, state the particular result and where to check it; avoid “everything is ready” when only one part of a larger matter has been finished while the customer still expects other work.
Scroll the table sideways to see all columns.
| State | Known fact | Message |
|---|---|---|
| Information | Rules described; no change request saved | Here is the method; the date remains unchanged |
| Pending | Request received; no confirmation | We received the request; the change is not confirmed |
| Done | Change confirmed in the responsible system | State the new date and where to check it |
The table proposes language for a fictional process, not a list of actions performed by Meet AI. A complete pending message is: “We received your request to move the appointment to Friday. The current appointment remains active until the change is confirmed; you do not need to resend the request.” Use the final sentence only when the request really is preserved and the team can continue it; text merely appearing in an unsent editor is not a saved customer request.
Keep polished wording from creating a false done
“Confirmed”, “I booked it” and “changed” describe states rather than politeness. If a model produced them from an informational knowledge base, compare them with real execution evidence. An article explaining the possibility of a change does not confirm a particular change to the customer's record. Even a correct AI source citation supports a rule rather than establishing that someone just performed an action in an external process or successfully saved new data.
The Meet AI assistant answers from available knowledge and does not manage bookings for an operator. A private draft may still need editing when its explanation resembles execution. Replace “I changed the date” with “this is how to request a change” when that is the actual help provided. Read the whole edited message: removing one verb does not help if the next sentence still promises confirmation of a nonexistent record or suggests the customer no longer needs to check anything. When choosing a system that would perform such operations itself, compare the tool categories in our guide to AI agents vs chatbots for small businesses. Which data and actions an assistant should be allowed to access in the first place is covered in a separate guide to AI agent permissions.
Microsoft HAX recommends making the tasks supported by an AI system clear. The information-operation distinction here is our application of that principle: make clear what the system can do.
Distinguish a missing reply from an uncertain operation result
No confirmation after a request may mean the operation failed or that only its confirmation was lost. Do not automatically choose either explanation. Read the current state in the responsible system before deciding whether another attempt is needed.
A customer message might be: “I do not have the result confirmed yet. I will check the current state before retrying so that a second request is not created.” This proposes work by someone with access to that read, not automatic checking of every system.
Repeated clicking therefore is not the default response to every uncertainty. If evidence shows the action completed, confirm that state; if it did not, use the agreed retry route. Track several operations separately when a task contains more than one. The new date may be saved while its confirmation message is pending; tell the customer about the completed change without falsely claiming that all subsequent steps have finished or need no further inspection by the team handling the case.
Leave a readable result rather than only closing the thread
Closing a thread is not evidence that every described action happened. Before closing, record a clear result: what changed, what did not and where the customer can see the current state. Technical identifiers or internal logs are unnecessary if the person can verify it in their own view. Broader AI case-resolution assessment covers the process; here you confirm a particular operation and its scope rather than deriving completion from the conversation's closed label.
For a team response template, prepare separate pending and completed versions. Do not give operators one friendly passage requiring them to remember to remove “done” in many cases. When the request leaves explanation and execution unclear, use one clarification question: its answer selects the next step but still does not prove that an operation happened. Consistent language joins information, request and confirmed result without giving the assistant additional execution powers or making a document an operational tool.
Questions about information and actual execution
Does “we received the request” mean the change was made? No, it confirms receipt only when the request was actually saved. Separately explain whether the existing state remains active and which confirmation the customer awaits. Do not use the phrase for content still in an editor draft; receiving a message, starting work and completing an operation are three separate facts requiring their own evidence rather than one shared reassuring sentence.
When can you say done? When the responsible system confirms a specific result and the replying person knows its scope. Name that result rather than using the general word alone, for example “The appointment was moved to Friday at 5 pm.” If you have not checked the outcome or part remains open, describe that status without claiming complete execution; a polite tone cannot replace real evidence of a change in the record.
