Requests in the Sado portal: what a request card holds and how to work with it every day
Sado AI team · · 4 min read
In short
Requests (Arizalar) is the portal’s list of what customers asked for and whom to call. A request appears after every call where the customer wanted something, or comes from a website form, an uploaded file or your CRM. The card shows a “What they need” line, the customer’s answers, the recording and transcript, and any booking. The list has views: New, Good leads, Call back, Appointments, Mine and All. A simple routine: each morning give every good lead and new request an owner, and leave no overdue callbacks by evening.
What a request is and where it comes from
The portal’s Calls section holds every conversation. Requests holds the work: what the customer needs, who owns it and what happens next. Requests come from:
- An incoming call: the customer asked a price, booked, or asked to be called back.
- A form on your website or Instagram.
- A list uploaded from a file, or an auto-call list.
- Your CRM or other software, through the API.
What’s on a request card
- The “What they need” line: the customer’s need in one sentence.
- The customer’s answers: each operator question is its own field.
- A short summary and the next step.
- The recording and full transcript, so you can listen if needed.
- The appointment time and callback time, if set.
- The assignee: who handles the request.
For example, a request that came in overnight: “What they need: swimming classes for a 7-year-old son, on Saturdays.” Answers: age 7, branch Yunusabad, best time Saturday morning. Next step: the receptionist calls back with the price and timetable. Opening the card, staff know at once what to do and don’t have to ask the customer anything again.
The views: who looks where
| View | What it shows | Who checks it |
|---|---|---|
| New | Requests nobody has looked at yet | Receptionist, every morning |
| Good leads | Callers who said they’re ready to buy | Salesperson, first thing |
| Call back | Requests with a callback time, overdue ones included | The assignee |
| Appointments | Upcoming meetings and appointments | Front desk or branch |
| Mine | Open requests assigned to you | Every staff member |
| All | Every request, searchable by phone or name | The manager |
The 15-minute morning routine
- Open Good leads: give each one an assignee and call them first.
- Go through New: read the “What they need” line and assign each request.
- In Call back, do the overdue ones right away.
- Check today’s Appointments. If a customer wants another time, move the booking to a free slot right on the card. If you cancel one, tell the customer yourself.
- After talking to the customer, mark Contacted; when it’s done, mark Done.
Handing a callback to the operator
The operator can call a customer from a request instead of your staff: one customer with the “Let the operator call” button on the card, many at once in Auto-calls by choosing portal requests — new ones, people who asked for a callback, or all. The result appears under Calls. An example (prices made up):
Sado: Assalomu alaykum, this is Malika from Nur optics. Yesterday you asked about glasses prices and said to call in the evening. Is now a good time?
Caller: Yes, go ahead.
Sado: Frames start at 350,000 so‘m, and with lenses from 600,000. It’s best to come in and choose. Tomorrow or Saturday?
Caller: Saturday afternoon.
Sado: Done, you’re booked for Saturday at three. Have a good evening!
Rules for working with requests
- Give every request to one person: a request that belongs to everyone belongs to no one.
- By the end of the day, no overdue requests should be left in Call back.
- Once a week, download the results to Excel and count how many requests became sales.
- If you use Bitrix24, a lead or deal is opened in the CRM after the call too, so staff keep working where they’re used to.
How the operator collects a request: AI operator for incoming calls. Price: 800 so‘m a minute, no monthly fee. Try it live.
Questions
What’s the difference between Requests and Calls?
Calls holds every conversation with its recording and transcript. Requests holds the work: what the customer needs, who owns it and the next step.
Do website form requests land here too?
Yes. If your website or form is connected, the request appears under Requests and the operator can call right away. The Sado team connects it; for developers: API.
Can requests be shared out among staff?
Yes: each request has an assignee, and staff see theirs in the Mine view. More answers: Sado FAQ.