Evose

Customer support

From new ticket to a cited reply

The agent drafts cited replies, packages escalations and scores every chat. Agents send, and team leads decide exceptions.

Contact sales
Example

Where work stalls

  1. 01

    When a policy changes, macros and help center articles lag behind, and customers get different answers to the same question.

  2. 02

    Escalations to engineering bounce back for missing versions, logs or repro steps, and customers are asked for the same details again.

  3. 03

    QA can only sample a small share of conversations, so service issues usually surface after a customer complains.

Work agents take on

  1. Request

    For every new after-sales ticket, draft a reply from the After-sales Policy, cite the exact section and leave it as an internal note for the agent. If it involves a refund over $75 or the customer is upset, flag it for the team lead instead

    • Open API · triggered by the helpdesk
    • Helpdesk (HTTP plugin, internal notes only)
    • Order lookup (HTTP plugin, read-only)
    • Support · After-sales policy
    • Support · Troubleshooting

    Run

    1. Read the ticket and order to find the issue type and warranty status
    2. Find the policy section and troubleshooting steps that apply
    3. Draft the reply with citations and suggest type and tags
    4. Edit and send from the helpdesk, with refunds and exceptions going to the team leadSupport agent Nina Park
    5. Log whether the draft was used as is or edited, for the weekly review
Example

Where people decide

  1. 01

    Agents review every reply before it is sent, and refunds, credits and exceptions are decided by the team lead

  2. 02

    A second-line engineer confirms severity and whether a new engineering ticket is needed

  3. 03

    QA deductions count toward an agent's score only after the team lead reviews them

Plan your rollout with us

Tell us about your teams and where Evose should run.

Contact sales