AI replies for customer support teams

Draft replies from the ticket in front of you, approve what goes out and share one playbook.

Use cases

Three jobs to hand to HARPA first.

01

Reply drafts from the ticket

Most tickets need the same five answers, in your tone, with this customer’s details. Draft them from the ticket.

  1. Open the ticket, with the whole thread on screen.
  2. Run /reply: FIND ON PAGE, then a type such as APOLOGY or ASK FOR INFO, or describe it.
  3. Adjust with SHORTEN or PROFESSIONAL.
  4. PASTE TO PAGE, read it, send it.

Good to knowIn a helpdesk HARPA reads what the page shows, so open the full thread first. It never sends for you.

02

Approve before it goes out

Automations save hours, but some steps need a person. Let the run stop and ask.

  1. Add an Ask step (YES or NO) and tick Wait for my answer in unattended runs.
  2. Give the next step a run condition, such as {{post}} = yes.
  3. Answer under Needs you at the top of the Inbox; the run carries on.

Good to knowAn Ask waits up to 24 hours. Without the box ticked, an unattended run ends at the Ask step.

03

One playbook for the team

Every agent should answer the same way. Build the reply commands once and share them.

  1. On harpa.ai/account, New space, then Upgrade to Teams.
  2. Invite by email. Commands, AI connections and one credit balance are shared.
  3. Lock the shared commands that must not change.
  4. Each agent switches to the space with the button at the top left.

Good to knowChats, memory, automations and the Inbox stay personal. Only the owner changes connections.

Free for desktop Chromium browsers

Put your browser to work.