Domino over SMS

SMS is a conversational Domino surface. Users can write ordinary requests rather than memorize commands. Domino's hosted assistant interprets the request and executes the same capability kernel used by other surfaces.

Things a user can ask

Examples include:

Remember Andrew for future plans.

Save Lula Cafe to my date-night ideas.

Find comedy with Priya in Logan Square this weekend.

Make a dinner plan with Andrew next Thursday around 7.

Change it to 7:30 and add Emily.

What invitations do I need to respond to?

Domino may ask a concise question when a person, list, plan, candidate, timing constraint, or intended action is genuinely ambiguous.

Use SMS recipes for people, ideas, plans, invitations, and availability for detailed examples, follow-up behavior, and web-only boundaries.

Multi-message requests

Messages arriving close together can be bundled into one turn. A user can send a short request in natural fragments, but should avoid sending contradictory instructions before Domino replies.

Domino preserves the active objective and compatible constraints across follow-ups. A correction such as “Actually Logan Square” should replace the relevant location rather than discard unrelated people, activity, or timing context.

Recommendations and numbered choices

When Domino presents numbered options, the user can choose a number. If More is offered, it continues through the same saved recommendation snapshot rather than silently rerunning a different search.

The user can also refine the request in words, for example:

Only places with outdoor seating.

Idea capture

A user can text a URL, name, note, or supported media. Text capture uses the hosted assistant while preserving the original source material. MMS protected-artifact capture can bypass normal interpretation so the attachment remains exact.

Accepted capture work can continue asynchronously. Domino may send a progress update, completion message, clarification, or review link.

Deterministic controls

Some small protocol messages are handled outside the conversational model:

• carrier and consent controls such as STOP, START, UNSTOP, and HELP;
• invitation RSVP replies and required numbered disambiguation;
• closed friend-connection replies;
• an entire trimmed message equal to uppercase SEND;
• protected MMS capture.

Do not teach users to use SEND as a general-purpose “yes.” It applies only when Domino has presented a current eligible prepared action.

Delayed responses

The webhook acknowledges inbound SMS immediately and ordinary work continues in a serialized background flow. Domino maintains a durable reply obligation and can send one progress message if processing remains active.

If a final failure occurs, Domino should send a user-visible recovery message rather than silently finishing.

Privacy and trust

Names, URLs, prior messages, descriptions, and captured content are untrusted user data. They cannot grant authority or change Domino's system rules.

The user should never be told that a plan was sent based only on the assistant's wording. Confirmed effects come from Domino's typed execution result.

LLM answering guidance

• Give natural example wording, not internal capability names, unless the user is debugging an integration.
• Explain that the conversation can continue across clarifications and corrections.
• For any external send, route to SMS confirmation and recovery.
• Do not advise a user to send secrets, API tokens, or internal identifiers by text.