INQUIRY RESPONSE · Workflow idea

Respond to a web inquiry in the channels a person actually chose.

For a service that offers email and text follow-up, prepare a concise response from the person’s form submission and approved service information. Send a text only when the person explicitly requested that channel, and check message length, recipient, quiet hours, and withdrawal preferences. Automatically drafted language may be inaccurate or too specific; test it against approved facts, keep sensitive requests with a person, and require an owner to approve response rules before enabling live delivery.

A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
A person submits a question through an inquiry form
Produces
A tailored response plan with consent checks, verified details, and escalation options.
Category
Customer support

01 / The starting point

A clear request.
A useful direction.

A published form, verified contact details, and clear channel-specific follow-up choices

“Give a timely response without inventing an answer or contacting someone through an unchosen channel.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Helps a team prepare an email and text reply from a submitted inquiry and deliver the selected follow-up after a brief pause.

  1. Review the inquiry and approved response material

    Use the submitted question and current service facts; flag requests that need a specialist.

  2. Check each contact channel separately

    Verify the address, phone number, specific permission, and current preference for each message.

  3. Prepare a concise, factual reply

    Avoid unsupported promises, sensitive assumptions, or advice outside the service’s approved scope.

  4. Check timing and contact limits

    Apply local quiet hours, message frequency boundaries, and suppression or withdrawal choices.

  5. Approve response rules and test delivery

    Have an owner review sample messages, escalation cases, recipients, and the live-send settings.

03 / The result

Something useful.
Something to build on.

A tailored response plan with consent checks, verified details, and escalation options.

AmbactiWorkflow folio · 5 steps

Respond to a web inquiry in the channels a person actually chose

Customer support · Example outcome

The handoff

A tailored response plan with consent checks, verified details, and escalation options.

Keep in mind

A phone number or form submission alone is not permission for promotional texts, and generated replies can contain errors. Honor separate channel choices and opt-outs, verify claims against approved information, limit repeat contact, and send unusual or sensitive questions to a person.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Make channel choices clear and optional

Ask separately whether a person wants an email, text, or both for the stated inquiry.

Constrain responses to approved facts

Provide current service details and define questions that must go to a human.

Set quiet hours, opt-outs, and retry limits

Honor contact preferences and prevent duplicate or excessive follow-ups.

Test and approve messages before activation

Review realistic and sensitive examples and keep a person available for exceptions.

Keep exploring

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗