# LOOP by mihu: The Contact Center Where AI Agents Are Colleagues | Mihu AI Launch Week · Day 3 · LOOP by mihu # LOOP by mihu: The Contact Center Where AI Agents Are Colleagues Seven channels in one inbox, a softphone in the same window, and an AI agent on the same threads as your team — co-pilot it, take it over, or let your rules decide when a team member steps in. Mihu AI Team September 2, 2026 10 min read v1.0.0 Launch Week · Day 3 Inbox · Softphone · Handoff · Copilot Your team One thread AI agent Your team and your AI agent work the same thread. The handoff takes four seconds, and the reason is written in it. In this article 1 What LOOP is (https://mihu.ai/ru/blog/launch-week-day-3-02-09-2026#what) 2 One inbox, seven channels (https://mihu.ai/ru/blog/launch-week-day-3-02-09-2026#inbox) 3 Three modes, and the switch in the header (https://mihu.ai/ru/blog/launch-week-day-3-02-09-2026#modes) 4 The handoff, second by second (https://mihu.ai/ru/blog/launch-week-day-3-02-09-2026#handoff) 5 Voice: the AI agent on the line with you (https://mihu.ai/ru/blog/launch-week-day-3-02-09-2026#voice) 6 Escalations you cannot miss (https://mihu.ai/ru/blog/launch-week-day-3-02-09-2026#escalations) 7 What the AI agent adds while a team member is typing (https://mihu.ai/ru/blog/launch-week-day-3-02-09-2026#copilot) 8 Contacts, appointments and tasks (https://mihu.ai/ru/blog/launch-week-day-3-02-09-2026#contacts) 9 Languages, presence and the things that ring (https://mihu.ai/ru/blog/launch-week-day-3-02-09-2026#languages) 10 What LOOP costs (https://mihu.ai/ru/blog/launch-week-day-3-02-09-2026#start) 11 Frequently asked questions (https://mihu.ai/ru/blog/launch-week-day-3-02-09-2026#faq) LOOP by mihu is the Mihu Contact Center: an omnichannel inbox and cloud call center where your team and your AI agents answer the same calls and the same messages, on the same screen. ## What LOOP Is Not a helpdesk with an AI agent bolted on. Not an AI agent with someone watching. Every setup that pairs AI agents with team members breaks in the same three places. The customer explains it twice, because the bot’s transcript lives in one tool and your team’s screen in another. Your team works in three windows — the AI platform, the softphone, the CRM — and every alt-tab is a place for context to leak. And nobody can say why a conversation reached a team member, because the reason was never written down. LOOP is built to fix that bridge. One workspace, one login, one conversation record: Your team gets a full contact center: voice, WhatsApp, SMS, email, web chat, Instagram DM and Facebook Messenger in one inbox, a softphone, transfers, contacts, appointments and tasks. Your AI agents — the ones you already built in Mihu — join a queue exactly like a team member does. You pick them from a list. That is the whole integration. You decide the balance , queue by queue, and change it whenever you like. Outside your working hours, the AI agent takes over automatically. And the work goes the other way too. A team member can hand a task to an AI agent — call this customer back, find out what they actually need, chase the document that never arrived — with a time on it if it is not for now. The agent makes the call, and what it learns is on the record before anyone opens the thread. It is not a second product. LOOP reads and writes the same AI agents, memory, knowledge, contacts and calendar your Mihu agents already run on. There is nothing to integrate. ## One Inbox, Seven Channels Everything a floor needs, on one screen that never navigates away. Open Inbox . Three columns: what is waiting, what you are doing, and what the AI agent knows. Your queues, as rows — you only see the queues you are on. Click one and the inbox filters to it. A new hire can be live on one queue without touching the rest of the floor. The conversation list — tabs for Open · Escalated · Resolved · All , and a switch from Conversations to Tasks . Every row says who is holding it, AI or team member, with a violet hairline for unread. Pin to top, mark read or unread, "unread from here". The thread — voice, WhatsApp, SMS, email, web chat, Instagram and Messenger land in the same conversation. Photos, videos, voice notes, documents, locations and contact cards, both ways. In the desk What it does Softphone, inbound and outbound Answer what arrives and dial out yourself. Mute, hold, keypad, recording — and a call widget that follows you around the app Transfer Mid-conversation, move a call or a thread to another queue, or send the call out to another phone number altogether. Warm briefs them first, blind sends it straight through, and the reason travels with it The contact record, live The customer’s CRM record sits beside the thread: fields, tags, pipeline stage, notes and every past conversation. Change it mid-call and the change lands at once — for your colleagues, for your reporting, and for the AI agent answering the next message Knowledge base Ask your own documents from inside the thread. The answer comes back with the source article attached, so nobody has to guess at policy Live call co-pilot On a call the AI agent listens to both sides, reads that same knowledge base, and puts the next line on screen as guidance. It never speaks — you do Templates Start an outbound WhatsApp or email from an approved template, with variables filled from the contact record — by you, or by the AI agent Quick replies Your own canned openers, translated into up to 16 languages, inserted in the language you pick Statuses and labels Name, colour and order the conversation states your operation actually uses; label each session with its verdict Calendar, Contacts and search open inside the same shell. Nothing reloads, so the dialer, your presence and every live subscription stay up while you look someone up. You never lose a call by opening the address book. ### Anatomy of the Desk One screen, three columns, and everything a conversation needs. This is what a team member is looking at while the call above is live. workdesk.mihu.ai / inbox Available RM 1 Conversations 6 4 • Support 2 • Sales 1 • Billing 0 • Reception Open Escalated Resolved 2 Marcus Reed Live call · warning light on the A22 Emma Ross 2 photos · damaged delivery Lauren Brooks Test drive — Thursday 10:00 held 3 Marcus Reed Reed Logistics · Fleet · Priority SLA 8 Human First Escalated to you at 14:05 — safety-critical . Fleet account found, roadside assistance already dispatched, ETA 25 min. Warning light on the FH — it came on out on the A22 motorway. Found your account, Marco — Volvo FH 500, priority SLA. Pull over safely, I’m getting a technician on this. Il camion è ancora in moto ma sono preoccupato per la sicurezza. Italian → English · “The truck is still running but I’m worried about safety.” Marco, roadside is 25 minutes out. Hazards on, stay behind the barrier — I’ll stay on with you. 4 Confirm the ETA Offer a courtesy vehicle Type your reply… Activity Capabilities Workflows 5 Live sentiment 35 negative Concerned about safety, urgent tone. 6 What the AI did ✓ Fleet account retrieved — priority SLA 14:05 · automatic ✓ Safety protocol · roadside dispatched 14:05 · automatic Book workshop slot — tomorrow 08:30 awaiting your approval Approve 7 Contact · CRM Company Rinaldi Trasporti Vehicle Volvo FH 500 Issue Engine warning AI Next appointment Tomorrow · 08:30 Workshop · 90 min Eight things are happening on this screen at once. Nothing on it needs a second tab. 1 Your queues, as boxes. A team member only sees the queues they are on, and the counts are live. 2 Who is holding each thread. A glyph on every row says AI or team member. A violet hairline means unread. 3 One conversation, every channel. Voice, WhatsApp, SMS, email, web chat, Instagram and Messenger in the same thread. 4 A draft you can take or leave. Suggested replies grounded in your knowledge base. Insert, edit or regenerate. 5 Sentiment as a number. Read live, in every language, with the reason in one line. 6 A visible action trail. Every lookup and booking, timestamped, marked automatic or awaiting approval. 7 Contact and calendar, in reach. The record and the next appointment on the same screen, with AI-filled fields marked. 8 The mode switch, in the header. Take the conversation from the AI agent, or hand it back, in one click. See the desk annotated, point by point → (https://mihu.ai/ru/mihu-contact-center) ## Three Modes, and the Switch in the Header Not three products — three settings. You met these on Day 2, on the queue's Automation card. Today is what they look like from your team’s chair. Mode Who does what Use it for Autopilot Mihu AI handles the conversation and sends the replies itself. It books against real availability, keeps the record current, and hands off to a team member the moment your rules say so. The questions that repeat: order status, invoices, opening hours, rebooking Copilot The AI agent drafts and suggests; you approve, edit and send. Anything touching money or a commitment waits for a team member to approve it — a setting, not a promise. Sales, and anything with a policy edge: financing, exceptions, goodwill Human First You handle it; the AI agent stays silent, with suggestions on demand. A full omnichannel inbox your team runs themselves. VIP accounts, safety, complaints, anything regulated Set the mode on a queue, on a channel, or on one conversation. Sales on Copilot, Support on Autopilot, VIP on Human First — one workspace, three answers. The customer never sees the switch. MR Marcus Reed WhatsApp · Service & Support Autopilot Copilot Human AI → Human — Rachel took over · 14:05 AI → Co-pilot — AI drafts, Rachel sends · 14:12 Human → AI — autopilot resumed by Rachel · 14:31 The switch is in the thread header. Every change is written into the thread with a reason. Step away and come back, and LOOP asks whether to take your conversations back from Autopilot or keep them with the AI agent. Nothing moves without you. ## The Handoff, Second by Second Four seconds, and the team member already knows everything. This is the moment every hybrid setup gets wrong, so here is exactly what happens. A live billing call, an AI agent on the line: Time Who What happens 02:31 AI Third mention of "charged twice". Sentiment drops to frustrated, confidence 0.94. Intent is now a refund, not a question. 02:32 AI Your flow rule matches: frustration past your line, a billing topic, a refund over €100. You set that trigger — the AI agent recognises that you already decided. 02:34 Team Routed to the Billing queue, to a team member who is available and holds the refund permission. The thread arrives whole. 02:38 Team "I can see the duplicate charge of €247 from the 14th — I'm refunding it now." No re-introduction. No "bear with me". 02:38 AI The CRM deal updates, the webhook fires, a follow-up task is scheduled. The team member did none of it. What arrives with the thread is not a summary someone has to trust. It is the objects themselves: The full transcript — the AI agent’s turns and your team member’s turns, in order, with who said what. The contact record and everything the AI agent retrieved — the €247 charge, the account, the policy. Live sentiment — a number, a label and the reason, in the customer's language. The actions already taken — the AI Agent panel's Activity log is read-only, written by the platform, so no invented row can pass as an AI action. The reason — written into the thread timeline, every time. Thread timeline · why it reached a team member AI → Human — outside the AI's knowledge, handed to the team AI → Human — the customer asked for a person AI → Human — guard rule "refund over €100" handed over to the team SLA breached — escalated to the "Billing" queue Negative sentiment — escalated to the "Billing" queue Overflowed to "Support 2" — the team was busy AI → Human — forwarded to the team (outside working hours) "Why did this reach a team member?" is a line in the thread, not an argument. And it goes back: when the hard part is done, your team member hands the thread back to the AI agent for the follow-up and the reminder. The baton moves both ways. ## Voice: the AI Agent on the Line With You One live call, four states, no call transfer. On messaging a handoff is a state change. On voice it is harder, so LOOP does it on the live call. The team member joins the same call the AI agent and the customer are on — the recording, the transcript and the conversation record never break. Button What happens Listen live Hear a call your AI agent is on, with a live transcript. Go back a few seconds, then jump back to live. Join call You are on the line while the AI agent keeps talking. Listen, then decide. Take over You speak; the AI agent goes quiet. Mid-sentence if you like. Hand back to AI agent The AI agent resumes with the same context. You can also steer the AI agent without taking over: Say a line and the AI agent speaks it in its own voice; Transfer and the AI agent announces the transfer, then connects the line; Mute the AI agent ; or End call with a goodbye message. And you can move the call off your own screen without ending it. While it is still running, send it to another queue — billing, the workshop, whoever should have had it — or transfer the line out to another phone number entirely, a branch or a colleague’s mobile. Warm if you want to brief them first, blind if it is obvious. Either way the thread, the record and the reason go with it, so nobody restarts the conversation. Incoming call · +39 348 … AI Customer Brief Who Marco Rinaldi · Rinaldi Trasporti Language Italian Key facts Volvo FH 500 · fleet · priority SLA Likely reason Engine warning reported yesterday Answer Answer with AI Decline Incoming calls arrive with the brief already written: who, company, key facts, sentiment and the likely reason. Human First on a phone number works the way a phone should: the number rings your team first. Every member of the queue rings, the first to pick up wins, and if nobody answers within the window you set (30 seconds by default) the AI agent picks up and greets. The AI agent as the fallback, not the gatekeeper. Copilot on a live call. The AI agent hears both sides and turns the call into a script as it happens. It never speaks. What it does instead is answer on your screen while the customer is still talking. Somebody asks where their order is, and by the time they finish the sentence the order is in front of you. They ask what the refund policy actually says, and the clause is there with the article it came from. It arrives as a Say next card, grounded in your knowledge base and in whatever you have connected. The customer is talking to a person, and the person already has the answer. This is not a voice trick. The same thing happens on every text channel, where the answer lands in the draft above the composer instead: the order status, the policy, the account detail, already written into a reply you can send, edit or throw away. If the team member drops, the customer is not left in silence: the AI agent takes the call back after a few seconds. ## Escalations You Cannot Miss When the AI agent stops, it does not go quiet. It raises an alarm. The hardest part of a shared desk is telling a team member, at a glance, which conversations need them. So each state looks different on purpose. Open Escalated · 1 Resolved JC James Carter Escalated Mihu AI handed this to a human — repeated frustration Take over LB Lauren Brooks Thursday at 10:00 is held for you — see you then. Mihu AI replying SM Sara Marino Can I move the service to Friday instead? 2 Three states, three different jobs: a red rail, an AI shimmer, an unread counter. State What the row looks like What it means Human · Copilot An unread counter "Answer me." The number is the only thing you need to read Autopilot A live AI shimmer, no counter "I've got this — stay out." Nobody double-answers a customer Escalated A red rail, pinned to the top, reason on the row "The AI agent stopped — you're on." One click to take over, and the handover is logged The conversation moves to the Escalated tab, the AI agent stops replying, and a handover strip appears in the thread with the reason. A desktop notification and a sound — an escalation is the one event we let interrupt a team member. And it reaches you even when the LOOP tab is closed: Alert me on this device is a browser push, no app to install. Escalations are triggered by the flow rules you set on Day 2 — knowledge gap, SLA breach, negative sentiment, a customer asking for a team member, a keyword — not by the AI agent’s own judgement. ## What the AI Agent Adds While a Team Member Is Typing Only when you ask for it. In Human First, the AI agent stays silent until you press the button. The right-hand column is what the AI agent knows: User Info , the AI Agent panel (Activity · Capabilities · Workflows), the CRM record with pipeline stages, Sessions and their labels, Tags , Notes , AI suggestions , Live Sentiment and AI Analysis . Draft with Mihu AI — a button above the composer reads the conversation and writes a reply. Pick the tone — Empathetic, Professional, Friendly or the AI agent’s own suggestion — then Insert , Regenerate , Dismiss or Approve & send . It needs no configured AI agent, so a team with no AI agent gets it from day one. Catch-up draft — a customer was waiting and nobody replied? The AI agent prepares the answer and asks you to approve it before Autopilot takes over. AI suggestions with a confidence score — the AI agent proposes an action (book the slot, update the field, open the ticket). You Approve or Reject . Sensitive changes never happen without the tap. Live Sentiment — a score, a label and the reason, updated as the conversation moves, in any language. AI Analysis on every conversation — sentiment, emotion, intent, knowledge gap, whether a team member was needed, satisfaction, resolution outcome, duration and language. AI and team conversations, the same fields. Ask the knowledge base — a question box over your own documents, with the source attached. Set how strict the match must be — Relaxed, Balanced or Strict — and Test this agent runs the exact retrieval it uses with a customer. Live translation — the customer's language stays theirs; you read and write in yours. Keep the original visible, translate your replies, and see "Sent in Italian" on every message. AI suggestions Approve or reject — nothing runs without the tap Book workshop slot — tomorrow 08:30 Confidence 94% Approve Reject Update contact · Vehicle: Volvo FH 500 Confidence 91% Approve Reject Send roadside protocol (WhatsApp template) Confidence 88% Approve Reject The AI agent proposes. A team member decides. Both are logged. Try this: put one queue on Copilot for a day. Count how many drafts your team sent unchanged. That number is the work you were paying your team to type. ## Contacts, Appointments and Tasks One record, one calendar, three authors. This is the test of whether AI and your team really share a desk: can both write to the same record and the same calendar? Yes — with a marker saying which one did. One contact record. In Autopilot the AI agent writes it. In Copilot it proposes and your team member confirms. In Human First your team member owns it outright. Custom fields, tags and pipeline stages are yours, so a conversation can move a deal. Sensitive field changes queue for approval. Every past conversation across every channel sits on the contact, with its analysis. An edit lands the moment you make it: the colleague who picks the thread up next sees it, your reporting counts it, and the AI agent answering the following message already knows. The AI agent fills it from the conversation. Nobody types up a record after a call. The AI agent reads the thread as it happens and pulls out the fields it can see — the company, the vehicle, the order number, the reason they got in touch — and puts each one where it belongs. What happens next is yours to set. The fields can queue as a suggestion with a confidence score, so your team member glances at them and approves with one tap, or they can go straight through to your CRM with nobody touching them at all. You set that per field, which is the part that matters. A corrected address can write itself; a payment term, a discount or a cancellation waits for a person. Either way the field is marked with where it came from, so a record nobody typed is still a record you can audit. One calendar. Either side can book, move or cancel, and a team member can override any of it. You decide how much authority the AI agent has on the schedule — always ask for approval , auto-approve minor changes , or full autonomy — and whether a team member confirms its bookings. Tomorrow Workshop calendar Booked by 08:30 Marcus Reed · Diagnostics — booked on the call Team 10:00 Lauren Brooks · Test drive — booked in chat AI 11:30 Sara Marino · Spring service — reminder sent AI 14:00 Avery Clark · Finance consultation — awaiting confirm Waiting Tasks — the outbound queue. Most of a contact center's value is outbound, and most outbound dies in a spreadsheet. Flip the inbox to Tasks and you have the calls and messages that should happen today: new leads, callbacks, reminders, win-backs, complaint follow-ups. Each opens with the reason it exists, the contact record and a suggested opening line. Create one for me , or for an AI agent — pick the AI agent, the contact, the channel and the due time, and the AI agent makes the call. A task does not have to be for a person, and it does not have to be for now. Hand one to an AI agent with a time on it — call this customer in three days, send that WhatsApp tomorrow morning, email the quote on Monday — and the agent does it when the clock says so, in your customer’s language, with the whole history already in front of it. It opens as an ordinary conversation on the desk, so anyone on the queue can step in mid-call. And it can finish the job on its own. If the call ends with a date agreed, the AI agent books it straight into the calendar, sends the confirmation, and sets the reminder that chases the no-show — no ticket, no handover, no person retyping a slot that was already spoken out loud. ## Languages, Presence and the Things That Ring The parts nobody demos and everybody needs by week two. 16 interface languages — Türkçe, English, Italiano, Español, Nederlands, Français, Deutsch, Português, Українська, Русский, Polski, Română, Български, Čeština, العربية, עברית — with full right-to-left layouts for Arabic and Hebrew. Live translation across 40+. Presence that means something — Available, Working, On a call, Lunch, Be right back, Out of office. Go idle and LOOP notices; set Lunch and it never overrides you. When you are not available, the composer locks: replies are paused until you are back. A visible activity log on your own account — every request made with it, newest first. Team management, roles and access logs stay where you set them on Day 2. Your own domain and logo on the desk. The same workspace runs under a partner's brand, out of the box. ## What LOOP Costs A monthly plan, free seats inside it, and usage you can read off a table. Contact center software is normally sold by the chair. You count your team members, multiply by a monthly licence, and every new hire is a line item before they have answered anything. LOOP does not put a price on a person. You pick a plan, and everyone you put on the desk is free inside it. The plan is what sets the ceilings: how many people you can seat, how many AI agents you can run, how many channels one of them may work, how many inbound and outbound email addresses you get, and what you are allowed to train an agent on. Seats stay free at every level, so growing a team is never the thing that moves your bill. ### What Your Team Costs, and What the AI Costs Inside the plan, only two things are metered: the minutes your team spends on the phone, and the work you hand to the AI agent. What your team uses What it costs WhatsApp, SMS, email, web chat, Instagram and Messenger Free, on every plan Voice €0.001 a minute, on every plan Neither of those two moves with your plan. Freemium pays what Enterprise pays. Everything the AI agent does is metered instead, per message or per minute, and what it costs is based on your plan . The bigger the plan, the less each AI message and each AI minute costs, so the busier you get the cheaper the work the AI agent is doing for you. WhatsApp and the other Meta channels, SMS and calls also carry their own carrier rates, and calls depend on where you are dialling. Every rate, plan by plan, is on the plans page (https://mihu.ai/ru#pricing) . That distinction is worth a second read, because it changes what you can do with the product. A team that has switched no AI agent on pays its plan and its phone minutes, and nothing else. Seven channels, the softphone, transfers, contacts, appointments, tasks and the outbound queue, with every message free. So the AI agent is never the price of admission. You can put your team on the desk first, work it for a month, and then turn an AI agent on for the one queue where the repetition is worst. That queue starts metering. The others carry on as they were. A worked example. Seven people on Starter, ten thousand minutes on the phone last month, every message answered by hand. One month on LOOP A team of seven Starter plan Seven seats included €100.00 10,000 voice minutes at €0.001 a minute €10.00 Messaging on seven channels worked by your team €0.00 AI agents and Copilot not switched on for any queue €0.00 What you pay €110.00 Seven people, ten thousand minutes, seven channels. A hundred and ten euro. Nothing in that bill was counted per person, so the seventh hire cost exactly what the first one did. Two things move it: outgrowing your plan, and deciding the AI agent should take some of the work. Seats are free inside your plan. How many you get is set by the plan you are on, and the larger plans stop counting altogether. Numbers you buy in-app , live in minutes. Connect WhatsApp, Instagram, Messenger, email, SMS and the web chat widget the same way. Two-factor authentication , GDPR and HIPAA flags per AI agent, recordings you control. What this replaces What you get instead An AI vendor and a separate helpdesk, joined by a webhook and hope One workspace, one login, one conversation record A softphone in one tab, a CRM in another, a chat tool in a third A desk where the AI agent is a colleague, not an upstream system Handoffs that arrive as a transcript nobody reads in time Handoffs measured in seconds, with the reason written in the thread An AI that answers first and a team member who mops up Human First numbers that ring your team first, with the AI agent as the fallback A monthly licence for every chair, whether or not it is filled One plan for the workspace, with every seat inside it free Try this: register, buy a number, open the Day 2 queue, and put one AI agent in it beside one team member. Take a call. Press Take over . Press Hand back to AI agent . That is the whole product, and it takes an afternoon. ## Frequently Asked Questions Can I let my AI agent take over during a call? Yes. Press Hand back to AI agent while the call is still running and the AI agent carries on from where you stopped, on the same line, with the whole conversation behind it. The customer hears no break and no hold tone. It works in both directions: you can take a call off the AI agent mid-sentence, deal with the hard part, and hand it back for the follow-up. Can my AI agent decide, and my team approve it? Yes, and that is the human-in-the-loop part. In Copilot the AI agent drafts the reply and your team member is the one who sends it. Beyond replies it proposes actions of its own — book this slot, update this field, open this ticket — each with a confidence score, and a team member approves or rejects it with one tap. You decide which actions and which fields need that tap, so a corrected address can go through on its own while anything touching money, a commitment or a sensitive field waits for a person. Every decision is logged with who made it. Do my AI agents and my team really work the same conversations? Yes, on voice and on text alike. An AI agent joins a queue the same way a team member does, and their turns sit in the same conversation, in order. Both write to the same contact record, so a field the AI agent filled mid-call is already there when a person takes over. That handover, in either direction, is the human-in-the-loop process — and the reason for it is written into the thread. What does a team member see when the AI agent hands over? The full transcript, the contact record, everything the AI agent retrieved, live sentiment, the actions already taken and the reason for the handoff, written into the thread. Does the customer notice the handoff? No. On messaging the thread simply continues. On voice your team member joins the same live call, so the customer hears one continuous conversation, not a hold tone. Can a team member give a conversation back to the AI agent? Yes. Take over from the AI agent, or hand it back, in one click from the thread header. On a live call the button says Hand back to AI agent. The change is logged with a reason. Can I see my customer’s CRM record on the desk, and update it there? Yes, once your CRM is connected. The record opens beside the thread, you edit it while you are still talking, and the change lands at once — for your colleagues, for your reporting, and for the AI agent answering the next message. If your CRM is not one of the ready integrations, you build the connection yourself with the Builder Assistant, which writes the integration and deploys it. Can a phone number ring my team before the AI agent? Yes. Set the number to Human First: every member of the queue rings, first to answer wins, and the AI agent picks up only if nobody does within the window you set. Can I buy a number and start taking calls straight away? Yes. You buy numbers inside the app and they are live in minutes. Connect WhatsApp, Instagram, Messenger, email, SMS and the web chat widget the same way, put your team on a queue, and the first call can land the same afternoon. How much do seats cost? A seat has no price of its own. Your plan decides how many you get, and every one of them is free. Your team’s messaging is free on every plan and their calls are €0.001 a minute. Is this a separate product from Mihu? No. It is the same platform with your team in it — same AI agents, memory, knowledge base, contacts and calendar. Nothing to integrate. ## Take your first call today Register on the free plan, buy a number and invite your team. Seats cost nothing, the messages they send cost nothing, and you add an AI agent to a queue only when you want one. Register free → (https://app.mihu.ai/register) Launch Week LOOP Mihu Contact Center Omnichannel Inbox Cloud Call Center Handoff Copilot ## Keep exploring Launch Week More ways to run your contact center with Mihu AI 👥 Launch Week · Day 2 #### Team, Roles, Logs, Queues, and Smart Routing Sep 2026 (https://mihu.ai/ru/blog/launch-week-day-2-01-09-2026) 🔒 Launch Week · Day 1 #### Domain, Security, and Identity Aug 2026 (https://mihu.ai/ru/blog/launch-week-day-1-31-08-2026) 🤖 Product #### Mihu Contact Center Product page (https://mihu.ai/ru/mihu-contact-center)