CUSTOMER SUPPORT INTAKE · Workflow idea

Give each support request a clear place to go.

Capture the customer and request details your team provides, then create a support case for follow-up. Check the resulting record so the request is attached to the right customer and contains the intended information.

A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
Support request
Produces
A support case record with the supplied information and a returned reference or creation status for the service team.
Category
Customer support

01 / The starting point

A clear request.
A useful direction.

A customer’s contact details and the issue information supplied by your team

“Create a new support case using the supplied customer, subject, and request details.”
An example request · Make it specific to your team.

02 / The work

6 tasks.
One useful outcome.

Organizes supplied customer and issue details into a new support case so the responsible team can review the request.

  1. Collect the request details

    Gather the customer information, subject, and issue description needed to record the support case.

  2. Check the customer match

    Confirm that the supplied contact information refers to the intended customer before creating the case.

  3. Review the case summary

    Make sure the subject and request description accurately represent what the customer or team provided.

  4. Create the support case

    Add the reviewed information as a new case in the team’s support queue.

  5. Verify the created record

    Check the returned case reference and confirm the details are available to the staff responsible for follow-up.

  6. Review any customer-facing response

    If a reply is prepared, have a support team member verify its recipient and wording before sending it externally.

03 / The result

Something useful.
Something to build on.

A support case record with the supplied information and a returned reference or creation status for the service team.

AmbactiWorkflow folio · 6 steps

Record a customer support request

Customer support · Example outcome

The handoff

A support case record with the supplied information and a returned reference or creation status for the service team.

Keep in mind

The created record reflects the information supplied and does not verify the customer’s identity or resolve the issue. Check the customer match and case details before relying on the record or contacting the customer.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Choose the support queue

Select the team location where new customer cases should be recorded.

Agree on required request details

Decide which customer, subject, and issue fields are needed for a useful first review.

Set customer-data access

Limit access to customer contact details and case information to staff who need them for support.

Test case creation and follow-up

Use a sample request to check customer matching, the saved case, and any review required before a customer message is sent.

Keep exploring

Prepare a support ticket

Turn a support request into a clear proposed ticket and let an agent review it before it is added to the support queue.

Review new customer support records

Bring newly added customer records to a support teammate so they can verify the details and decide whether follow-up is needed.

Review customer support issues

Help a support team turn selected customer conversations into clear ticket drafts, with human review before records or replies change.

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗