SMS confirmation and recovery

SMS has deterministic safety controls for external sends, RSVP, consent, and recovery.

Exact SEND

When Domino has prepared an invitation or other supported consequential action, it presents the exact action for review and establishes a short-lived confirmation.

To authorize that prepared action, the user's entire trimmed inbound message must be:

SEND

The following do not count:

• send
• Send
• SEND!
• yes
• send it
• SEND please
• a message containing SEND plus another request

Exact SEND is handled outside the model. Domino revalidates the actor, SMS surface, principal, plan revision, recipients, destinations, authorization, and readiness before executing the group effect.

Expiry and edits

Prepared actions expire after a bounded window. A plan or draft edit supersedes an existing preparation for that subject.

If the user edits the time, audience, place, or message after preparation, Domino must prepare and present a new exact action before another SEND can work.

Retry behavior

A retry of an already consumed prepared action replays the stored result without creating a second effect. The user should not repeatedly send SEND to troubleshoot an unclear response; first inspect Domino's reply or ask what happened.

Local simulator

The local simulator suppresses prepared-action consumption. It leaves the preparation open and creates no invite, notification, queued SMS, or external message. A simulated success is not evidence that another person was contacted.

RSVP replies

RSVP controls are tied to a specific invitation. A terse acceptance or decline is deterministic when one invitation is eligible. If several invitations could match, Domino asks the user to choose from a numbered list.

Do not apply a bare “yes” to an arbitrary invitation.

Start over

When the conversation is working on the wrong objective, the user can clearly ask to start over or state the new unrelated request. Domino should supersede incompatible prior work rather than silently blend two objectives.

Missing information

When Domino asks a clarification:

• answer the question directly;
• include a correction to another constraint only when intended;
• do not provide internal IDs;
• if the saved choices no longer fit, refine the request in words.

If Domino appears stuck

1. Read the most recent Domino reply.
2. Answer any explicit clarification or numbered choice.
3. If processing is active, wait for the progress or terminal reply.
4. If the objective is wrong, clearly start a new request.
5. If a send result is unclear, ask Domino for the current plan or invitation status before attempting another send.

LLM answering guidance

• Format exact SEND on its own line.
• Explain what has been prepared before telling a user to confirm it.
• Never suggest working around expiry, supersession, recipient changes, or readiness checks.
• Never describe simulator suppression as a live send.