Refund RaiderConsumer action, with teeth Back home

Intake workspace

Keep the live call clean. Switch to integrations only when the agent needs more authority.

Live call

Start the conversation here. Let the agent decide when it needs tools, not the other way around.

This is the main product surface: voice first, transcript second, manual correction third. The integrations tab exists so the live call does not get buried under setup widgets.

Best current fit: cancellations, refunds, replacements, and billing-fix cases where the agent can progress through policy evidence, inbox context, or browser authority.

Live agent mode

Google missingGmail optionalBrowser runtime after case open

Manage integrations

Voice-first intake

Talk it out. Let the agent drive the call, then pull in connectors only when needed.

The voice agent can gather the facts, tell you when it needs Gmail access, search the inbox once connected, and open the action case without dropping you into a blank form.

Mock intake mode

Inbox status

Gmail not connected

Voice can search Gmail after one browser consent step.

Current merchant

Still collecting

Tell the agent what happened in plain English.

Workflow stage

Waiting for intake

The manual form below stays in sync as the agent works.

Live agent

mock-agent

Config state

mock

Mic permission

unknown

Preferred transport

unknown

I’m Refund Raider. Tell me what happened, and I’ll structure the action case for you.

Voice can drive the flow. The manual form stays available as a visible fallback.

Context drop

Paste the messy context only if the call needs more signal.

Use this when the live agent needs an order email, support reply, merchant URL, or a screenshot-derived clue to structure the case faster.

Order email, support message, or refund summary

Best inputs: order email, support reply, merchant URL, screenshot, PDF receipt, or a short complaint.

Review what the agent understood

The call stays primary. These fields are here so you can correct the case before it opens.

Merchant nameMerchant URLIssue summaryIssue typeDesired outcomePayment methodPurchase dateMerchant support emailProof uploadAttach a receipt, screenshot, or PDF. Text-like files work now; screenshots and PDFs still depend on OCR provider setup.

Once the case opens, the agent can build the plan and decide whether it needs browser automation.