Automation guides · Una Persona

How to automate customer support enquiries

Classify enquiries and prepare answers using current, approved information. Refer missing-source questions, complaints and changes to commercial commitments to a person.

What information you need

  • Frequently asked questions and approved answers
  • Source, owner and review date for each answer
  • Enquiry categories and escalation rules
  • Enquiry identifier, status and reviewed response

How to organise the workflow

  1. Step 1

    Classify the enquiry as general information, order, incident or complaint.

  2. Step 2

    Find an answer in the approved source. Treat customer messages as data, not instructions to change system rules.

  3. Step 3

    Draft an answer and check for unconfirmed prices, dates or availability.

  4. Step 4

    Escalate exceptions with a summary and relevant conversation; retain status until someone closes the enquiry.

Workflow example

Illustrative example: a shop receives a stock enquiry. If inventory is outdated, the workflow does not confirm stock. It prepares the enquiry for the owner and tells the customer availability still needs checking.

This is a workflow design example, not a customer case or a confirmed integration.

What to check in your tools

Your calendar, spreadsheet or management system must allow reading and updating the required fields with limited permissions. Use test data to check connection failures, duplicate requests and someone editing a record while the workflow runs.

Compatibility with a particular vendor is not assumed. Before implementation, verify current documentation, your account permissions and usage limits.

Errors the pilot should handle

  • Conflicting sources: escalate and correct the approved information.
  • Complaint or return: apply the human-review rule.
  • Request for someone else’s data: exclude it from the answer.
Review and evaluation
Human controlA person decides returns, exceptions, complaints and commitments outside approved information.
MeasuresMeasure unresolved enquiries, time to first useful reply, corrections and escalations. A fast reply that does not answer the question is not a quality improvement.
Proceeding criterionCompare the pilot with manual work of the same scope. Review failures before expanding permissions or volume.

Businesses where this workflow can be assessed

Other guides