Platform

Everything your team needs to run AI customer experience

Design the agent, connect it to your tools, launch it on every channel and prove what it resolved. One workspace for support, CX design, product and engineering.

Fernway · Returns agentProduction · v42
Resolution rate84%↑ 12 pts
CSAT4.7of 5
Median handle time1m 12s
Cost per resolution$0.29
ConversationsResolved by AIHanded off
14 days agoToday
Recent conversations
Can I swap my bike for an e-bike on Saturday?ENResolved48s
¿Puedo cambiar la fecha de recogida?ESResolved1m 04s
Billing question about a double chargeARHanded off3m 20s
Where do I return the helmet?ENResolved36s

01Channels

One agent on every channel your customers use

Build once and launch the same agent on web chat, in-app, WhatsApp, SMS and voice. It answers in the customer's language and keeps the thread when they switch channels.

  • Every channel from the same playbooks, with per-channel tone and length.
  • 40+ languages detected from the first message, no extra setup.
  • Clean hand-offs to your team in the helpdesk you already run, with the full transcript.
Read the channels guide
Returns agentLive on 5 channels
Web chatFernway · “Can I swap my bike for an e-bike?”English
In-appHalden Home · “色が違いました”Japanese
WhatsAppLumen Bank · “¿Puedo cambiar la fecha?”Spanish
SMSCalder Health · “शुक्रवार शाम?”Hindi
VoiceBrightline Telecom · Billing help

02Playbooks

Write how your best people work. The agent follows it.

A playbook is a plain document: the goal, the rules, the steps. Reference policies and actions inline, and Scout, our build assistant, suggests tighter wording as you go.

  • Plain language that support leads can own without waiting on engineering.
  • Inline references to knowledge and actions, checked every time you save.
  • Versioned so every change has an author, a reason and a way back.
Read the playbooks guide

Goal

Help customers return or exchange an order in one conversation. Keep replies short, warm and specific.

Rules

Follow Returns policy for every decision. Offer an exchange before a refund. Never ask for card details.

Steps

  1. 1Find the orderAsk for the order number, then use Look up order.
  2. 2Check the windowInside 30 days, offer an exchange or a refund. Outside, run the exceptions flow.
  3. 3Confirm and closeSend the return label and tell the customer when the money lands.

03Flows

Flows for the moments that need control

Refunds, identity checks, anything with money or risk attached. Draw the exact path once and the agent never improvises there, while playbooks handle everything around it.

  • Branching logic on any value the agent has collected or looked up.
  • Guardrails that hold even when a customer pushes back.
  • Mix freely with playbooks inside the same conversation.
Flows in the docs

04Knowledge

Answers that come from your policies, not a guess

Connect PDFs, help centres, Notion pages, sheets and URLs. Parley keeps them in sync, cites the source behind every answer and tells you which questions it could not cover.

  • Always current with scheduled syncs and change alerts.
  • Cited answers your team can check in one click.
  • Gap reports that show which articles to write next.
Read the knowledge guide

05Actions

Actions let your agent get things done

Look up an order, issue a refund, rebook an appointment. Connect your helpdesk, CRM and commerce tools, or call your own API, and decide exactly what the agent is allowed to change.

  • Ready integrations for the tools support teams already run.
  • Your own APIs with typed inputs, secrets and timeouts.
  • Permissions per action, with approval steps where money moves.
Read the actions guide

06Analytics

Analytics that show your CX impact

Resolution rate, cost per conversation, satisfaction and hours handed back, each traced to the conversations behind it. Topics show product teams what customers keep asking for.

  • Resolution you can audit line by line, not a black-box score.
  • Topic trends grouped automatically across every channel.
  • Exports to your warehouse on a schedule or by webhook.
See traces and reporting

07Collaboration

Collaboration built into every change

Support, CX design, product and engineering work in one place. Comment on a playbook line, review a change before it ships and see who changed what, and why.

  • Threads and mentions on any playbook, flow or test.
  • Reviews before a change reaches production.
  • Roles so everyone can see, and the right people can ship.
How changes ship

08For developers

Down to the code when you need it

Version agents from your terminal, trace every step a conversation takes, and write code wherever a playbook isn't enough.

See your own conversations on Parley

Bring a playbook and a week of transcripts. We’ll show you the resolution rate before you sign anything.