Super Intelligence.

What you are looking at

This is the home screen of the console: the whole call-center floor on one page. The top row of tiles shows what is happening right now — calls waiting in queue with the longest current wait, active calls across every agent, the service level (the share of calls answered inside 20 seconds against a 90% target), and abandoned calls for the day.

The second row is the day's scoreboard: calls handled, sales closed, revenue booked today and how many agents are online. Below it, Live calls lists every conversation in progress with the caller, number, direction, call type, the agent on the line and a running timer. The Agent floor at the bottom shows each agent — Eve and the other AI agents next to the human staff — with their status (on call, wrap-up, available) and calls taken.

How to use it

1. Leave the wallboard open on a screen in the office, or keep it as your first tab: every tile updates as calls come in and end.
2. Watch the queue and SLA tiles together. If the queue climbs and SLA drops under target, more callers are waiting than your agents can answer, so put another agent on the phones.
3. Click any row under Live calls to open that conversation and listen in. The agent floor below shows at a glance who is free to take the next call.
4. Use the search bar at the top right to jump straight to a customer, case or call from anywhere in the console.

What you are looking at

The Call Center is the complete call log. Each row is one call with its call ID, the customer, whether it was inbound or outbound, the call type (billing, tech, support, sales, prospecting, follow-up), the agent who handled it, the duration and the disposition — how the call ended: resolved, transferred, escalated, callback scheduled, voicemail or no answer.

Calls handled by Eve sit in the same list as calls handled by people, so a manager reviews one record of the business rather than two. Agent names are colour-coded so you can scan the list and see who took what.

How to use it

1. Click any row to open the call. The call panel shows the full details and lets you play the conversation in Eve's voice, so you hear exactly what the caller heard.
2. Set the outcome from the panel with one click and the call's disposition updates in the log and on the wallboard.
3. Press Simulate incoming call to watch a new call land in the log and on the wallboard, or Open latest call to jump to the most recent conversation.
4. Scan the disposition column for Escalated and Callback scheduled each morning; those are the promises still owed to customers.

What you are looking at

Customers is the client book. Each row shows the company, the contact with email and phone, the plan they are on, their location and an account status — active, lead, or failed when a payment did not go through.

The panel on the right summarises the book: total customers, how many are active, monthly recurring revenue, open cases and calls today. Under it are the quick actions you use most — initiate a call, send an email, send a message or open a new case.

How to use it

1. Click a customer to open their record. It shows every call and every support case for that customer, newest first, so anyone who picks up the phone knows the history before saying hello.
2. From the record, press Call to start a call handled in Eve's voice, or send an email or message without leaving the page.
3. Use the status badges to work your list: Lead rows are prospects to follow up, and Failed rows are customers whose payment needs attention.
4. Search by name, company, email or phone from the bar at the top to find a customer in a large book.

What you are looking at

Cases is the support desk. Each row is one ticket with its case number, the subject, the customer, the channel it came in on (chat, SMS, phone, email or portal), its priority (urgent, high, normal, low), when it was last updated and its status — open, pending, resolved or closed.

Cases opened by Eve during a call land here next to tickets raised by staff, so a problem a caller reports at 11 p.m. is waiting on the desk with full context the next morning.

How to use it

1. Click a case to open its detail panel and read the whole interaction history: what the customer said, on which channel, and what was done.
2. Work the list by priority. Urgent and High tickets that are still Open or Pending are the ones to clear first.
3. Open a case from a customer's record as well. The same tickets appear there, so the history follows the customer wherever you look them up.
4. Look for repeated subjects — several customers reporting the same problem usually means one fix, not many tickets.

What you are looking at

Campaigns is where outbound messages are run — SMS, voice calls and email blasts to a list of contacts. Each card shows the campaign name, the channel, the list it targets and how many contacts are on it, the exact message being sent, and a status: sending, scheduled or paused.

The progress bar and the four counters under each campaign tell you how it is performing: messages sent against the list size, messages delivered, replies received and opt-outs. In the demo the sends are simulated; nothing leaves the server.

How to use it

1. Read a campaign left to right: a big gap between sent and delivered points to bad numbers or addresses, and replies against delivered tells you whether the message is landing.
2. Keep an eye on opt-outs. A rising count means the message or the timing is wrong, so pause the campaign and rewrite it.
3. Voice campaigns are placed by Eve, so a lapsed customer gets a real conversation rather than a recording, and any reply becomes a call in the Call Center and a record on the customer.
4. Use Scheduled to line up reminders, such as renewal notices 14 days before a plan renews, so they go out on time without anyone pressing send.

What you are looking at

Agents is the team roster. Every agent who answers calls appears here, AI and human side by side: Eve, Nova and Dispatch Bot are tagged AI, and Marcus, Priya and Jordan are tagged human.

Each card shows the agent's live status — on call, wrap-up (finishing notes after a call) or available — plus the number of calls they have taken, their average call length and their CSAT, the customer-satisfaction score from callers.

How to use it

1. Use this screen to balance the floor. If several people are in wrap-up while the queue is building on the wallboard, that is where time is going.
2. Compare average call length and CSAT across agents. A short average with high satisfaction is the pattern to copy; long calls with low satisfaction point to a script or training gap.
3. Because AI and human agents are scored the same way, you can see which call types Eve should take on her own and which should be routed to a person.

What you are looking at

Stripe Updates shows the purchase funnel and payment activity. The three tiles at the top count the last 12 hours: people who clicked through to checkout, payments that were successful, and payments that failed.

Below, each row is one payment event with the time, the outcome (active, lead or failed), the customer's email, the plan they chose and the amount. It puts money next to the calls, so you can see what the phones are bringing in.

How to use it

1. Check the Failed rows first. Each one is a customer who wanted to buy and could not, and a call or message straight away usually saves the sale.
2. Compare clicks against successful payments in the tiles. If many people reach checkout and few pay, look at the price or the checkout step itself.
3. Match an email in this list to the Customers screen to see the calls and cases that led up to the purchase.
4. Lead rows reached checkout without completing; they belong in a follow-up campaign.

What you are looking at

Web Stats reports traffic to your website over the last 12 hours, with bots and internal traffic stripped out. Suspected humans is the number of real visitors; raw page hits is every request before filtering, so the gap between the two shows how much of your traffic is noise.

The two tiles underneath are the visits that matter most: checkout views (people looking at the payment page) and demo opens (people trying the product). They sit in the same console as your phone numbers, so you can compare website interest with call volume.

How to use it

1. Compare checkout views here with the clicks and payments on Stripe Updates. Many views with few payments points to a problem on the payment page.
2. Watch demo opens after a campaign goes out. A jump shows the message is driving people to try the product.
3. Use suspected humans, not raw hits, when you judge whether traffic is growing. Raw hits are inflated by crawlers and scripts.

What you are looking at

Portal Access is the security log for the console itself. The console sits behind two-factor sign-in: a user enters their password, a one-time code is sent to their phone, and they need both to get in.

The tiles count the last 12 hours: sign-in challenges issued, codes sent, successful logins, bad codes, bad passwords and blocked attempts. The table lists each event with its time, the event type, the IP address it came from and the path it tried to reach.

How to use it

1. Review this screen daily. A run of code_bad or bad-password events from the same IP address is someone guessing, and that address will appear in the blocked count.
2. Match successful logins against your own staff. A login_ok at an unusual hour or from an unfamiliar IP address is worth a question.
3. Because the console runs on your own private server, this log is the full record of who reached your customer data and when.

What you are looking at

Reports is the management summary. The four headline figures are monthly recurring revenue, the number of customers, total cases handled, and average CSAT across every agent, AI and human.

Under them, Calls handled — last 14 days charts daily call volume, so you can see busy days, quiet days and the weekly rhythm of the business at a glance.

How to use it

1. Open Reports at the start of the week. The bar chart shows whether volume is rising or falling and which days need the most agents on the floor.
2. Read CSAT next to call volume. If satisfaction holds while calls increase, the team, Eve included, is keeping up; if it dips on the busiest days, add capacity on those days.
3. Use MRR and customer count as the outcome measures. The other screens show the activity that drives them.