alori
← Partner playbook

The Alori demo script: a 60-minute demo that starts with the client's screen

14 min read

Short answer

Run the demo in seven parts over 60 minutes. Agree on the goals, then let the person who does the work every day show you how they work today. After that, show how a request flows in Alori, how the team answers one, how the bot answers one, what you imported and set up, and who does what next. Build it on the client's own data, keep the bot to drafting replies until they trust it, and let the daily user decide when to switch.

Win the client

06/10

This guide is for Alori partners who book demos with businesses. It comes after discovery: you already know the business, its tools and who decides. The examples use a support team moving off a help desk, which is the most common case. The same seven parts work for sales, scheduling or invoicing: swap "ticket" for "lead", "job" or "invoice".

Why the client shows their screen first

When you open with your own screen, you show features. When the client opens with theirs, you learn how they actually work: the views they live in, the statuses they rely on, the tags their reports depend on, the copy-and-paste between two tools that eats their day. Those details only come out when someone does the work in front of you.

Every part of the demo after that answers something they just showed you, so they see their own job in it. And the person who uses the tool every day feels heard, which matters most when that person decides when to switch.

Before the call

Spend a few hours on this. The more of their own data is in the app, the better the demo.

Checklist0 of 8 done

The deck

Start from our templatedownload the deck (PowerPoint) or see it as a PDF. It has the 27 slides below, with every part to change in blue [brackets], notes on what to say under each slide, and dashed boxes where your client's screenshots go. It opens in PowerPoint and Keynote, and in Google Slides through File, then Import slides.

Keep it short and put the client's own numbers in it. A section title slide opens each part, so everyone knows where you are. The outline:

Ready to copy
1. Welcome to Alori, [client]. One line on the move: "[old tool] to Alori, nothing lost, nothing paused."
2. Agenda, 60 minutes: the seven parts below, with their minutes.
3. What we'll do today: four goals. The last one is "[daily user] decides".
   Under them: "Nothing changes for your customers while you decide."
4. [Daily user], show us your [old tool]: where requests come in, your go-to replies, how you tag, what slows you down.
5. How a request flows in Alori: every channel, one inbox, the bot reads it, then one of two paths.
6. Your inbox: To handle, Waiting, Snoozed, Closed, and the filters.
7. How [daily user] answers: everything about the customer on one screen, then the six moves.
8. How the bot answers: where and how it answers, what it knows, what it can look up.
9. You choose how much it does: bot first, team first, or the bot drafts (where we start).
10. Routine for the bot, judgment calls for the team: two lists, set together on the call.
11. Every answer shows its work: why it handed off, its sources, "Fix this answer".
12. What's connected, and what's left: one row per tool, each with its status.
13. What came over from [old tool], and what stays behind.
14. Your saved replies and your tags, with how often each tag is used.
15. Live test: three requests, start to finish.
16. From today to go-live, at [daily user]'s pace.
17. Who does what next: one column for the client's manager, one for the daily user, one for you.

The 60-minute plan

MinutesPartWho leads
0 to 51. Goals for todayYou
5 to 152. They show how they work todayThe client
15 to 203. How a request flows in AloriYou
20 to 304. How the team answersYou
30 to 455. How the bot answersYou
45 to 556. The import and setupYou, with the client
55 to 607. Next stepsEveryone

Part 1: Goals for today

Start with a round of names and roles, theirs first. Then show the agenda and the four goals, and say out loud that they will share their screen before you do.

Ready to copy
Thanks for joining. In the next hour we want to do four things:

1. Walk through how you work today, with you driving.
2. Look at your saved replies and how they come over.
3. Show you how the bot drafts and you check and send.
4. And then [daily user] decides: is this easy enough to adopt now, and when?

One promise: nothing changes for your customers while you decide.
The call is recorded, so anyone who couldn't make it can watch it later.

The manager will often add something here ("we also do this by hand every week"). Write it down. It's usually the next thing you'll automate for them.

Part 2: They show how they work today

Ask the daily user to share their screen and handle one real request from start to finish, the way they would on a normal day. You listen. Interrupt only to ask how something works.

Ready to copy
You drive, we listen. Show us a normal day, the way you really do it.
Take one real request, an easy one is fine, and walk us through it from the moment it comes in until it's done.

Cover these four, with the questions behind them:

Ready to copy
Where requests come in: email, chat, phone, social messages? Which is busiest? Which phone system takes your calls?
Your go-to replies: the ones you send every day, and the ones you never use.
How you tag: when you add tags, which ones matter, and who reads them. Does a report depend on them?
What slows you down: the clicks and copy-pastes you'd love to skip. What other tool do you open to answer?

Write down every "it would be helpful if": a copy button, a one-click action, a column with the waiting time, the list of what they closed this week. Some people are so used to their tool that nothing annoys them. "What takes you the most time?" always gets an answer. Before you share your screen, say back what you heard in a few lines, and name what you'll set up for them.

Part 3: How a request flows in Alori

Show one picture of the path, then the inbox.

  • Every channel lands in one inbox: email, website chat, phone, texts and social messages.
  • The bot reads each one first, with the help center, saved replies, Company memory and, for a verified customer, their orders and billing.
  • Then one of two paths. A routine request: the bot answers it and closes it, marked "Solved by Nora". A request that needs a person: the bot hands it to the team, with why and a drafted reply.

Then open Conversations: To handle (waiting on the team), Waiting (on the customer), snoozed (back when you said), closed, and the filters by channel, owner and bot. Point at the statuses that match theirs.

Part 4: How the team answers

Open the same kind of request they showed you in part 2. Show that everything about the customer is on one screen: one thread for email, chat and calls, every past ticket from their old tool, the customer's orders and subscription beside it, the drafted reply, and their saved replies above the reply box.

Then the six moves of answering a ticket yourself:

  1. From their own address. They connect their email once, and answers leave from it.
  2. Pick a saved reply. Their old macros, one click above the reply box, with the customer's name filled in.
  3. Add tags, from More actions › Tags, or let a saved reply add them.
  4. Close it, or set it to wait until the customer replies.
  5. Merge two tickets from the same customer.
  6. Take over from the bot in one click when it's on a ticket.

Part 5: How the bot answers

This is the longest part, because it's where trust is built. Show the bot's page: where and how it answers on each channel, with its rules in plain words; what it knows (their help articles and facts, with the counts); what it can look up (Shopify and Stripe, read-only).

You choose how much it does, and you can change it any day

  • Bot first: it answers every new message right away and hands off anything on the team's list.
  • Team first: it answers only when nobody on the team has replied within 2 minutes.
  • The bot drafts (where we start): the team answers everything, and the bot writes a suggested reply for each.

When someone on the team replies in a chat, the bot steps back from that chat until someone presses "Let Nora answer".

Approvalsthe bot drafts the reply from the help center, Company memory and the customer's orders. The person checks it, edits the words, sees the sources and the reason. They send it, and a thumbs up or down teaches the bot for next time.

Routine for the bot, judgment calls for the team.

Propose two lists and set them together on the call, in plain words in the bot's instructions:

Ready to copy
The bot answers on its own:
- Where is my order, and what's its tracking?
- Which plan am I on, and when does it renew?
- Did my payment go through? Can I get my invoice?
- How-to and setup questions the help center answers

Straight to the team:
- Refunds and returns
- Cancellations
- Damaged or missing items
- An unhappy customer
- Anything the bot isn't sure about

Order and billing answers come from their real data.

The customer is verified first (signed in on their site, or an email that passes the sender check). The bot reads Shopify and Stripe live and answers with the real details, and every lookup is shown to the team in a hand-off. It never changes an order, a subscription or a charge: refunds and cancellations stay with the team.

Every answer shows its work.

Open a hand-off and click "Why handed off": the reason, the rule it followed and the facts it used. Under any answer, Source shows exactly what it read. "Fix this answer" corrects it, and its next answer uses the fix.

Part 6: The import and setup

Show what's done and what's left, so nobody has to guess.

ItemWhat it isStatus
ShopifyTheir full order historyConnected
StripeSubscriptions, invoices and payments, read liveConnected
[Old tool] historyCustomers, tickets, help center, internal articlesImported
[Daily user]'s accountAccept the invite, set a passwordTo do
[Daily user]'s emailConnect it, so replies leave from their addressTo do
TagsThe list is in hand, loading into AloriIn progress
Saved repliesWe have the titles, we need the full textWaiting on you

Then what came over, side by side: customers and organizations became customers and companies; tickets became conversations, with every reply and file; private comments became team-only notes; the help center came over with its old links redirected; internal articles went into Company memory, team-only. Say plainly what stays behind (triggers, automations, SLAs, views) and ask which ones they rely on, so you rebuild those in Alori.

Finish with their saved replies and tags: how macros become Replies, how a Reply can add a tag when it's sent, and their top tags with how often each is used. Ask the questions you still need answered: which reports read the tags, which tags the old tool added on its own, who checks the numbers in week one.

Part 7: Next steps

A live test: three requests, start to finish.

Two routine ones the bot solves (an order status from Shopify, a renewal date from Stripe), and one it hands off with why, the order it found and a drafted reply, for the person to finish. Warn them first: once their email is connected, a reply sent from Alori reaches the real customer.

From today to go-live, at the daily user's pace

Ready to copy
Today: demo and first look.
[Day, time]: weekly touchpoint, same time every week. What worked, what to fix, what's next.
Next: approvals. The bot drafts, [daily user] checks and sends, with [old tool] still running.
[Daily user]'s call: switch when they say go, timed around their busy season.

Tell them how you'll support themone shared channel for questions and changes, answered fast; on day one you read every bot reply and hand-off; and the bot's rules are sentences, so they tell you or change them themselves.

Who does what next.

End on one slide with three columns and read it out:

Ready to copy
[Manager]: send the full text of each saved reply; tell us how each tag gets added; tell us which phone system takes your calls.
[Daily user]: accept the invite and set a password; connect your email; try the bot and rate its answers; list the old tool's rules you rely on.
[Your agency]: load the tags and replies; set the bot's rules with [daily user]; book the weekly touchpoint.

Book the touchpoint before you hang up. Then do your column first and tell them when each item is done.

Questions you'll get, with short answers

"Will the bot answer customers without us?"

Only if they want it to. It starts by drafting replies, and they move each channel to answering on its own when they're ready.

"What if the bot says something wrong?"

Each answer shows its sources, and the team can take over any conversation. "Fix this answer" corrects it for next time.

"Can the bot refund or cancel?"

No. It reads Shopify and Stripe but never changes an order, a subscription or a charge. Those stay with the team, with what the bot found already in the ticket.

"Can it look like what we have now?"

Close to it. Statuses, tags, fields and saved replies come over or get set up the same way, and they can ask for changes in plain words.

"Do we lose our history?"

No. Customers, tickets, notes and the help center come over, and old help center links redirect.

"What does it cost?"

Point to the pricing page, or give your own price if you bundle setup and support.

Tutorials to watch before your first demo

Questions

Another question? Write to us from the chat, real people answer.

They can't tell yet which parts matter to them. After they've shown you their day, every part of the demo answers something they showed, and they see their own work in it.

Because nothing changes for their customers while they decide. The team sees every draft, learns to trust it, and turns on answering channel by channel.

The person who uses the tool every day, and their manager. On your side, whoever will set the app up afterwards, so they hear the requests firsthand.

Write it down, say you'll check, and come back with an answer. Small changes to their own app can often be made in chat the same day.

For a team switching the tool it works in all day, no. If you only have 30 minutes, keep parts 1, 2 and 7, and show parts 3 to 5 on the one request they showed you.

Next guide · 07 · Win the client

Price custom software

Setup fee and retainer, anchored on the value for the client

Your first client starts here

Turn your account into an agency, build your app, and add your first client today.