Launch notes, dashboard improvements, email upgrades and safety controls — straight from the SIMCOAI team.
Two direct voice models for your AI front desk. Explore the preview, watch the trailer and learn how pilot access works.
Explore speech-to-speech Read the launch story
Product news and improvements from the SIMCOAI team, as they ship.
Showing all 233 updates.
Choose exactly what the AI asks before it books. The new Questions tab in Bookings lets you add your own questions, such as a gate code or a paint finish, set each one as free text, yes or no, or a pick from a list, and put them in the order you want. The answers show on every booking.
Bookings now show the details your customer gave while booking, such as their address, postcode, vehicle, registration, condition and any special request. They appear under the service in your bookings list, in full when you open a booking, and in the booking notes.
Call Studio and the support phone now release your microphone when a connection fails or you refuse access, reset mute after the other side hangs up, and ignore double clicks and late connections so a retry starts cleanly. Call usage is also no longer counted twice if a call status update arrives more than once.
You can call the demo receptionist from our homepage again. It now uses our normal calling experience, with microphone, sound and end-call controls.
The demo is a fictional conversation with up to six replies and a three-minute limit. No real appointments, refunds, emails or callbacks are created.
Call Logs now groups calls by phone number. Choose a number to see every call from that caller, then open any call to read it as a conversation, with what the receptionist said on one side and what the caller said on the other.
Calls on a free trial are no longer cut off when the monthly AI allowance is used up, so you can test your receptionist as much as you need. Your usual allowance applies once your trial ends.
Order lookups in conversations now reread stored details instead of treating an earlier conversation snapshot as current.
Changed or deleted orders no longer return from that snapshot when a lookup is empty or unavailable. Email searches keep literal characters in the address.
Order and refund conversations now compare complete phone numbers, keeping different numbers with the same ending separate.
Supported UK formats still match, and older matching orders remain visible even when unrelated newer orders share the same number ending.
Usage processing now keeps one saved request and checks ownership before recording its outcome.
Older uncertain outcomes are checked against recorded invoice confirmations. Missing or conflicting evidence remains on hold for review.
Caller recognition and customer records now compare complete phone numbers, so different numbers sharing an ending stay separate.
Supported UK number formats still match. Older matching records remain available even when newer records belong to other callers.
Pay-as-you-go processing now checks that its invoice outcome is saved before treating the entry as completed.
An already saved confirmation can resolve a lost response. Entries no longer awaiting processing are protected from later error updates.
Pay-as-you-go usage entries now retain their recorded outcome when the same activity is processed again.
Entries already invoiced retain their amount and invoiced status. Existing account limits and rates still apply.
Leaving an unfinished booking now clears its withdrawn time options from the conversation, helping keep later choices tied to current offers.
Ordinary replies still retain current options. Withdrawing an unfinished request does not cancel a confirmed booking.
If your requested day is unavailable, suggested alternatives now stay on or after that day and retain a morning or afternoon preference.
Requests beyond the booking window do not fall back to earlier dates. Suggested times still need your choice and the remaining booking checks.
When you explicitly accept a single recommended package, the receptionist now retains that choice when you give your preferred day.
Discussing a recommendation does not select it. Unclear choices still need clarification, and selecting a package does not create a booking.
A suggested time written as 1:35 is now checked against available appointment starts before it is read aloud. This helps prevent an afternoon start being described as morning.
Day recommendations also retain their checked offers, so you can choose one on the next turn. A recommendation does not create a booking.
Text test calls now retain the booking details and withdrawal state needed for the next turn. Saying to leave an unfinished request keeps it withdrawn while you discuss something else.
Starting a new request can resume collection. Withdrawing an unfinished request does not cancel an existing confirmed booking.
If you cannot supply a required vehicle registration, the receptionist can collect other details first. Its next collection reply now keeps the reminder that registration is needed before the booking can be confirmed.
Clear, checked booking details can now move directly to the next question. Simple vehicle confirmations use the detail already held, helping avoid an extra wait.
Questions, uncertainty and service-condition discussions still receive a considered response. Required details and final confirmation continue to apply.
Asking which day is recommended now checks availability for the service you selected. A longer appointment no longer receives suggested start times from another service.
Choosing an offered Monday keeps that offered date. Asking for next Monday checks the following week instead.
Saying you do not have a detail no longer replaces vehicle information you already supplied. The receptionist keeps a request for registration aligned with the detail currently being checked.
If registration is unavailable, other details can be collected first. A required registration still needs to be supplied before the booking is confirmed.
A saved refund request now remains a saved result if a later order update fails. The receptionist explains when that associated update needs checking.
Background recovery is now enabled for eligible refund order updates. If follow-up is interrupted, it can resume without submitting another refund.
Refund-related order updates now preserve current order details and check for a conflicting edit before saving.
An order update that cannot be verified does not produce a successful update event. Phone replies describe a recorded refund approval without claiming that a payment or external delivery has completed.
If a connection error interrupts the response after a new request is saved, the assistant can check that exact request before reporting the result.
It does not submit the request again to perform this check. If the saved result cannot be verified, it does not claim success.
The assistant now checks again immediately before saving a new booking, refund, callback or escalation request if the conversation has moved on while preparing the request.
This helps prevent an older response from saving a request after it has been superseded. It does not undo a request already submitted for saving.
If the receptionist cannot interpret a reply during booking details, it now returns to the question it was collecting instead of asking an unrelated general question.
Your unfinished details are preserved. An unclear reply does not confirm a booking, and you can repeat your answer to continue.
When you ask what a booking detail means or why it is needed, the receptionist is now guided to explain it and give you room to respond, rather than immediately asking for the same detail again.
Your unfinished booking details are kept while you ask questions. You can continue when ready or leave the request.
AI and phone access checks now use current saved subscription and plan-feature eligibility. Suspended accounts are explicitly blocked at these checks.
Turning off renewal still preserves eligible access for the current period. A failed account check does not grant access.
The receptionist checks saved changes before reusing business reference information during a phone conversation. Edited, unpublished or deleted entries refresh on the next lookup.
Expired AI memories are left out of the reference information prepared for new answers.
When the receptionist creates a booking, refund, escalation or callback request, its email and enabled integration updates are now recorded alongside the saved request.
Interrupted update processing can resume separately, with checks to avoid queueing the same message twice. The conversation can continue without waiting for email delivery.
If email processing stops before its delivery result is saved, the message is now flagged for checking. An uncertain message is not automatically sent again.
Ordinary failed deliveries continue to use their scheduled retry checks.
Once a booking or other request is saved, the receptionist can continue without waiting for its update emails to finish sending.
Customer messages keep your business branding and reply address. Failed email processing can be retried separately, with extra checks to avoid sending an accepted message again because its delivery record could not be saved.
The receptionist can handle a service choice or price comparison with fewer delays before replying, while keeping your booking requirements.
If a caller gives a clearly labelled detail and asks a question in the same turn, that detail is now kept while the question is answered. Side questions pause collection without losing the unfinished booking.
Your receptionist keeps the letters and numbers already supplied when you spell a postcode or registration in parts. Restarting postcode spelling does not duplicate the letters. Spoken postcodes are read back for confirmation before the receptionist moves on.
Short answers such as “half past ten on Monday” receive a time acknowledgement. An unfinished “half past” answer gets a question about the missing hour. Names and addresses receive an immediate acknowledgement, unclear parking answers get a simpler follow-up, and a booking review does not repeat the full list when you acknowledge it without confirming. After you confirm the details, the receptionist moves clearly to email verification.
Your AI receptionist now writes ordinary booking replies around what the caller actually says. Greetings, questions and changes of direction can pause detail collection. If a caller no longer wants an unfinished request, the receptionist can leave it without continuing the booking questions.
Required details, checked availability and successful booking confirmation remain controlled by the booking system. Clear package choices use the list the caller heard, while the AI writes the spoken response. Replies to straightforward details can begin while the call record finishes saving.
If the business reaches its AI usage allowance, the call now explains that clearly instead of repeatedly asking the caller to say the same thing again. Withdrawing an unfinished request remains possible when the AI cannot run.
Your receptionist can start asking the next booking question sooner after you give a clear detail. Completed exchanges stay available during the call, helping it continue without repeating the same preparation.
Clear requests for the cheapest or most expensive package use the published prices when there is one matching choice. Missing prices, equally priced choices and questions still need clarification. Booking confirmations continue to depend on a successfully saved booking.
Offline checks show shorter preparation waits. We are monitoring real calls to measure the improvement callers hear.
Your phone receptionist acknowledges booking details and uses more natural follow-ups. When you ask a question, describe what needs cleaning, or are unsure about a requirement, it can respond to your situation before asking for the next detail.
You can give several clearly labelled details together without being asked for each one again. Separate statements about private parking and access to water and power can also be collected together. Required checks and confirmation still apply.
Spoken registrations understand numbers such as “seventy five”. Postcodes can be spelled a little at a time, and uncertain interpretations are read back for confirmation. Asking “again?” repeats the current question, while an unanswered final review gets a short follow-up instead of the entire summary again.
Checks use transcript-based examples and simulated conversations. Simple answers keep the quick response path.
The receptionist now keeps each booking answer aligned with the question it asks. Vehicle make and model are held separately, so corrections keep the other detail and receive a fresh confirmation.
If you do not know a required registration, the receptionist can collect the other details first and then return to it. Your booking cannot be confirmed while a required detail is missing. Cleaning descriptions and other sentences are rejected as registrations.
Questions about the business return to the same booking step. Spelled registration and postcode details cannot start email collection or replace your contact number, and saved contact details remain separate from details you have spoken.
If your latest usage details are still loading, Growth now shows its included 50 premium requests in the fallback display. Your enforced allowance remains the same.
When billing dates are unavailable, monthly usage calculations keep their fallback dates aligned with the month being evaluated. Checks also confirm that published plan prices, active add-on prices and live usage totals agree.
The add-on page now includes Workflow API Messages and the Voice Growth, AI Growth and Operations bundles that were missing from the dashboard. Each uses the current account availability and price; connections that are still being prepared remain unavailable.
Your setup checklist now links directly to the settings for each task, with shortcuts to billing and usage. Default names such as “Your business” stay marked as missing until you enter your business name, and phone setup tasks appear only when your plan includes them.
Call Studio now links to text testing so you can check everyday questions before starting a voice test. The link explains that text tests use your AI allowance and can create records, so sample customer details are recommended.
Your phone receptionist keeps the chosen package and requested date when you give the time in a separate reply. Short package selections with a clear recognition error are matched only when one service fits, and ambiguous choices still need clarification.
Short email readbacks finish speaking through background noise and presence checks such as “hello”. Corrections still interrupt. If you ask whether the receptionist is there after the readback, it acknowledges you and asks for confirmation. Booking reviews use a concise condition description while keeping the full details in the booking record. Longer greetings keep complete sentences, so the opening stays brief and does not cut the receptionist’s introduction midway.
You can change the customer contact number in Email Branding. Booking confirmations use your saved company phone number, and custom email contact details can follow that number automatically.
Your phone receptionist recognises spoken dates such as “the twentieth of this month” and updates the date being checked when you change your mind. If you ask for another date without naming one, it asks which day suits you instead of repeating the old times. Requests beyond the available booking window receive an explanation.
Vehicle corrections keep the replacement details, with a confirmation question before moving on. Spoken registration letters and digits are read back as a registration, while registration-like answers are not accepted as a vehicle make and model. Changing the agreed date requires a fresh review of the booking details.
Checks cover varied dates, calendar boundaries, corrections and an isolated booking replay. The existing booking checks and verification requirements remain in place.
Your phone receptionist now uses your business identity and the name or role chosen in your greeting and instructions. Without a custom identity, it describes itself as your business’s AI receptionist.
Chosen receptionist wording is preserved in speech. Replies avoid introducing the service behind your receptionist, including when an answer arrives in small pieces. Offline checks cover questions during bookings, retained caller details, interruptions and early reply delivery. The AI and recording notice remains in place.
We have completed a customer email branding setup using the business’s own logo, colours, service information and contact details.
The branding appears on verification emails, booking confirmations and updates, and requests for supporting documents. Each message keeps the code, appointment status or secure link needed for the customer’s next step.
Everyday receptionist conversations now respond to what the caller actually says. Greetings, service choices, dates, booking details and availability questions use conversational responses instead of fixed questionnaire lines.
The receptionist can discuss choices, answer questions during a booking, acknowledge useful details and help callers explain uncertainty. Simple questions get brief answers; explanations can take a few sentences when needed. Required details, fresh diary checks and verification still apply.
Customer booking emails now show the business name, service and appointment time. They no longer invite customers to open the business dashboard or include internal booking notes.
The receptionist now remembers a confirmed service choice and keeps the booking name you give during the call, even when a different name is saved on your customer record.
For bookings that collect vehicle details, it reads back the make and model and registration for your confirmation. You can reject a misheard detail and provide it again.
Email confirmation and the final booking review are separate steps. A correct email proceeds through the required verification checks without an unnecessary text-link offer.
We have updated the software supporting sign-in, email delivery, file uploads, live connections and connected services to keep these features maintained and address known security issues.
Checks covered sign-in token verification, passkey setup, email attachments, upload limits, booking conversation handling and connection messages. Your existing plan and billing settings remain the same.
We have updated the software supporting email delivery, file uploads and live connections to address known security issues and keep these features maintained.
Checks covered email attachments, reuse of email connections, successful uploads, rejection of oversized files and live connection messages. These updates do not change your plan or how you use these features.
After a booking is complete and the receptionist invites you to say bye, a goodbye heard as “five” now ends the call politely.
Booking name collection also handles “put it on the…” when a caller supplies their name.
This correction applies only to that closing prompt. Numbers given for appointment times, booking details or verification codes continue through their usual checks.
We are trialling a more efficient way to connect receptionist calls on one selected account, with its existing voice selection preserved.
This is a limited pilot. Other accounts continue with their current calling settings, and customer plan prices have not changed.
When you give an email address during a booking call, the receptionist reads it back, asks whether it is correct, and waits for your answer. It no longer adds a text-link suggestion to that confirmation.
Requests such as “Can you send it to…” now keep the supplied address through confirmation. After two unsuccessful attempts, the receptionist can offer a text link so you can type the address instead.
Offline checks cover email corrections, a simple yes, and interrupted readbacks. An incomplete readback still needs confirmation before a verification code can be sent.
Call openings now pronounce AI within a complete sentence instead of speaking its letters separately. The greeting and recording notice remain protected, and speech during the opening is ignored.
Clear service selections, checked appointment choices and routine booking details now avoid unnecessary response steps. Ambiguous requests still receive clarification, and booking checks remain in place.
Brief speech connection failures now receive a bounded recovery attempt. Connections also stay active during protected openings. Call response timing is being monitored against the one to two second target; live listening verification is still pending.
Spoken postcodes now accept number words such as fifteen alongside individual letters. Call interruption handling stays active while speech is waiting to play, and a new caller response clears older queued speech.
The greeting and call disclaimer remain protected until they finish playing. Speech during the opening is ignored rather than saved or queued. Listening begins after the greeting and disclaimer finish. AI pronunciation has also been adjusted to avoid unnecessary pauses between its letters. These changes have passed offline postcode and audio playback checks.
When two callers choose an appointment at the same time, saving the booking now checks the remaining capacity before accepting it. If another booking has filled the time, the receptionist asks for another day or time.
Configured appointment capacity is respected, overlapping reschedules are checked, and cancelled appointments release their capacity. Concurrent booking checks and standard and realtime booking completion checks passed without paid calls.
Correcting your postcode during booking review now updates the saved details and asks you to confirm them again. If you have not supplied the replacement postcode, the receptionist asks for it.
Having electricity without a tap no longer counts as having both. Partial or uncertain access prompts clarification or a team review before the booking can proceed. Offline regression checks passed.
The receptionist can correct obvious email transcription slips, such as “gnail.com” to “gmail.com” or a misplaced dot before a recognised email provider. It reads the corrected address back and asks you to confirm it before using it.
Email corrections now apply only to the complete provider domain, so similar text in your email name or a longer custom domain stays unchanged. Spoken domain endings are kept as supplied, “Google Mail” is recognised as googlemail.com, and malformed email addresses prompt a repeat instead of being shortened to a different address. If the suggested address is wrong, say so and the receptionist will ask for a replacement. These changes passed offline checks.
When support approves an account usage reset, monthly usage counters can restart without removing your past conversations or call records. New activity counts from the reset onwards, and the usual billing-date renewal still applies.
Your account keeps its existing plan allowances, active phone numbers and billing history.
Your receptionist keeps the appointment day separate from the date of an event you mention. Rejecting an email now clears it until you supply and confirm a replacement.
Booking calls ask for the service address and postcode separately. A spelled postcode is no longer saved as a street address, and you can use words such as Hotel and Delta to spell postcode letters. Incomplete details still need clarification.
Selected appointment times are read from checked availability, and email corrections stay cleared across caller turns. Unclear fragments containing mostly digits are not accepted as a street address.
Regression checks passed. Live call behaviour remains under monitoring. A booking is confirmed only when the booking workflow succeeds.
Your receptionist now keeps your chosen package when you select an offered appointment time. Times beyond the first available appointments are checked before being described as taken.
You can ask to correct the service address during booking review. The receptionist collects the replacement address and asks you to confirm the updated details before proceeding.
Your receptionist now receives the specific reason a booking detail needs clarification, so it can explain what it could not capture and ask a focused follow-up in natural language.
Booking conversations also recognise requests such as “put it under Jake”, retain a chosen package while collecting other details, and keep vehicle information from replacing the caller’s name. Clearly spoken postcodes continue the booking; uncertain characters need clarification.
These changes passed offline transcript regression checks and an isolated booking-flow check. Live call behaviour remains under monitoring.
Phone booking conversations keep your chosen package when you provide another detail, reducing repeated package questions. Unclear requests to change a package still need clarification.
The default response wait is now 45 seconds. Calls allow at least a further minute after asking whether you are still there, and the response wait starts after the assistant finishes playing its reply.
Offline checks cover remembered choices, playback timing and cancelled silence timers. Live call behaviour remains under monitoring.
Your receptionist now uses the conversation to understand which booking package you choose, including relative price choices and corrections. A general request for a valet or agreement to a time does not select a premium package.
Booking replies use natural wording. When your package choice is unclear, the receptionist asks for clarification before booking. Spoken postcodes with separate letters and number words are recognised, while incomplete or ambiguous details still need clarification.
These changes were checked against the reported call transcript, real AI interpretation checks and isolated booking tests. Live call behaviour remains under monitoring.
Asking to make a booking now continues with your booking details instead of repeatedly reading back an email saved in your customer details.
This affected booking conversations where a saved email was treated as an address the caller had just supplied. Emails you provide during the call still receive a readback for confirmation, and corrections still replace the previous address.
StreetShine’s receptionist profile now uses its business name consistently and explains its three mobile detailing packages more clearly. Booking questions, cancellation enquiries and requests for help have clearer instructions for the next step.
Package prices, opening hours and the existing booking process are retained. Refund requests still require the team’s approval, and callers are not promised an appointment, transfer or callback until the relevant action is confirmed. The configuration was checked against saved settings and an offline booking scenario.
Choosing “the cheapest one” now selects the lowest-priced bookable package when there is a clear choice. Your receptionist keeps that selection while you choose an appointment day, instead of asking for the package again.
Explaining that you have a wedding or another event on a later day keeps the appointment day you requested. Saying “first available slot” now selects the earliest time offered, subject to a fresh availability check. Unclear speech keeps previously collected booking details.
When you phone to make a booking, your receptionist now uses the number you are calling from without asking you to dictate it. It keeps that number when you provide an email or answer later booking questions.
You can give a different contact number at any time. If your number is withheld or you are calling through the browser, the receptionist asks for a contact number. Corrected numbers replace the earlier booking answer, preventing repeated phone-number questions.
Supported live calls now use a dedicated listening mode while collecting email addresses, keep it active through readback and corrections, then return to ordinary conversation listening once the email is confirmed. Spelling an email address aloud keeps leading letters, spoken numbers and explanations such as “B for Bravo”. If the address arrives in separate parts, the receptionist keeps the letters while asking you to continue.
Requests such as “can you use this email?” now receive a direct readback for confirmation. Correcting an address starts a fresh confirmation, and unfinished spelling does not bring back a previously rejected email. You can still choose to type your details using a text link.
Your receptionist now remembers when you choose the number you are calling from, even when you have also supplied an email. An address and postcode given together are kept together, and natural parking answers such as “driveway” and “private parking” move the conversation forward.
Email confirmation recognises the address actually read back. Answering a booking detail no longer triggers another availability prompt while a required question is pending.
Quick replies such as “yes” are no longer discarded by an extra timer. Collected booking answers and the latest assistant question stay available during longer calls, while interrupted replies are marked so older questions do not become current again.
Speech recognition vocabulary now prioritises each business’s services and relevant booking terms, keeping complete phrases and reference digits. These changes add no extra waiting timer or processing request.
Each business can keep its own booking questions and free-text requests. When an explicit service requirement needs an exception, the receptionist can note an alternative arrangement for review before confirmation.
Saying you are looking to book a service now continues the conversation instead of asking you to wait. Spoken email requests such as “can you use” are kept separate from the address, and rejecting an address clears it before you give a replacement.
Text-link offers recognise more ways of asking whether you would like a link. Confirmed-booking follow-ups repeat the booked service, date and time, with the demo diary notice where applicable. Choosing the number you are calling from stays recorded, and driveway or private parking answers move on to the next booking question.
These changes passed offline conversation checks and booking verification checks in an isolated test account. Live call behaviour remains under monitoring.
Your receptionist now sends an offered typing link when you agree, waits while you complete the form, and lets you return to saying your details if the text has not arrived. An unsuccessful send no longer leaves you waiting for a link.
Spoken email confirmation keeps the address that was read back. Required booking questions about contact details, vehicles, service locations and access are checked before confirmation, with a summary for you to confirm. Demo diaries are explained as separate from existing website bookings.
We also fixed repeated ampersand encoding when editing business descriptions. These improvements were checked with offline call scenarios and isolated booking tests; audible call quality remains under monitoring.
Our status page now has consistent SIMCOAI branding and gives you a simpler overview of service availability, with individual checks and incident updates you can expand when you need more detail. Recent incidents, resolved history and known issues are easier to find on mobile and desktop.
The page is hosted independently of the SIMCOAI platform. If fresh checks cannot be reached, it shows the last confirmed report with its date and clearly marks current availability as unconfirmed. It retries automatically, without presenting an old report as a current all-clear.
Service groups now use a compact list with aligned availability labels and clearer expand arrows, making individual checks easier to browse on desktop and mobile.
When you ask to escalate a request, your receptionist now acknowledges that you want the team to review it before confirming your email address.
Previously, an email saved earlier in the conversation could trigger a repeated readback without explaining the next step. Contact confirmation still applies before the request is submitted.
We fixed a spoken-email problem where a receptionist could read back one address, then use a different address after the caller said yes. Requests such as “Could you use my email address…” now use the same address for the readback and confirmation.
If an email is unclear or includes repeated separators, the receptionist asks for a careful repeat instead of guessing. A replacement address still needs its own confirmation before a verification code can be sent.
Call Studio now shows microphone mute and sound-off controls with distinct, consistent colours in dark and light mode. Muting your microphone no longer turns the button unexpectedly white.
We also refined button feedback, tightened the call view and made audio settings easier to use on smaller screens.
We fixed a call-start problem that could end a Call Studio voice test immediately, before your receptionist spoke. Affected voice calls now accept the initial connection notice and continue into the conversation.
The fix also applies to incoming calls using the affected voice mode. Call permissions, account allowances and call authentication continue to apply.
Your dashboard now pauses notification checks while its browser tab is hidden. When you return, it checks for new notifications immediately and continues its normal updates while you use it.
Notification checks also share a request when a connection is slow, reducing repeated background activity. Your existing notifications remain available, and account access checks keep their normal timing while the dashboard is visible.
The receptionist now repeats your email address and waits for you to confirm it before sending a booking verification code. A corrected address is checked again, and you can ask for a text link to type it instead.
When you use the details link, the call waits while you type and picks up the submitted form without needing you to speak again. Rejected email addresses stay rejected, so the conversation does not return to an old, incorrect address.
Short spoken time choices are understood in the booking conversation. If “three” sounds like “free”, the receptionist checks what you meant. Appointment options share a date once, and services with fixed start times offer those actual times.
After a booking is confirmed, asking whether everything is done keeps that booking confirmed. Your own appointment is no longer mistaken for a time someone else has taken.
The website now keeps a more consistent balance of headings, images and spacing on desktop monitors and smaller browser windows. Dashboard cards adapt to the space available, with more room for their content. Documentation pages also keep their full reading width when the navigation menu is tucked away.
If you choose an appointment and ask a question in the same sentence, the receptionist now answers the question instead of jumping straight to asking for contact details. Questions spoken alongside an email address also stay part of the conversation. Questions about access and other facilities keep the relevant business information available while you are booking.
Refund policy and process questions are kept separate from your reason for requesting a refund. A useful answer is no longer replaced by another request for details. Reasons you have already explained remain available throughout the call. If you ask for an email readback after dictating an address, the receptionist repeats that address so you can check it.
Complete order references can move on without an extra pause, and straightforward refund requests can reach the next step sooner. Partly spoken references and email addresses still have room to finish. Appointment availability is checked against current records, and bookings still require the applicable verification. Spoken appointment times keep their morning or afternoon meaning when replies arrive in parts. Plain greetings and simple appointment choices also reach the next step sooner.
Selected calling profiles can now use extra recognition vocabulary while collecting names and email addresses, then return to ordinary listening for the rest of the conversation. Supported replies begin speaking complete sentences while the rest of the answer is prepared. Profile instructions and verification rules continue to apply, and a voice failure ends with a clear message or the permitted team handoff.
The receptionist now moves directly through routine booking details, checks verification codes and acknowledges completed bookings without an extra conversational step. Questions about prices, service differences and unusual situations still receive a conversational answer.
Supported English calls use natural turn detection, with room for pauses when dictating contact details or correcting yourself. Split email details can finish before the receptionist responds, and an unfinished utterance cannot create a booking. Replies can begin speaking sooner, and business reference information is reused briefly within each call. Availability, identity checks and verification still use the current records.
Offline and text-based checks passed, including booking verification, duplicate prevention, split emails and interrupted speech. Audible response times remain under monitoring.
The receptionist now recognises half-past appointment times when speech recognition writes “half” as “0.5”. Unclear decimal fragments no longer become five-past times. The selected appointment time stays consistent when you give your email address, and unavailable-time answers use the actual diary result.
Phone replies now use the details needed for the current request, recent exchanges and relevant earlier answers. Standing instructions are shorter while privacy and verification requirements remain in place. Regression checks cover the half-past correction and email sequence. Audible response time and conversation quality remain under monitoring.
Saying “I don’t care anymore”, “never mind” or “forget it” now takes priority over an earlier booking request or question. The receptionist stops collecting booking details and no longer carries an interrupted question into your withdrawal.
Ordinary greetings and service enquiries now use the conversation model to respond naturally. Questions about prices can receive an answer without an added booking-details prompt. These changes passed offline checks; live conversation quality remains under monitoring.
The dashboard tour now includes 24 detailed steps with practical examples, covering business information, receptionist settings, bookings, testing and everyday work. The guide stays in place while you scroll and use the dashboard. Jump to a step, minimise the guide, return to a highlighted control or pause and resume later. Steps adapt to your plan, and moving through the tour does not save settings, purchase anything or start a call.
When the receptionist proposes a specific service, saying “Yes, please” now keeps that choice instead of returning to the service menu. Asking for a later appointment after a whole-day availability offer now gives later choices within that day.
Standard calls retain earlier caller turns through interruptions. More booking intake answers begin speaking as the answer is generated, while booking confirmation still waits for the actual result. A short silence cutoff no longer replaces a genuine answer. Later-slot answers state a shared date once instead of repeating it for every choice. A controlled standard-call test measured 2.09–3.40 seconds to audible replies, with no call errors or bookings created. The two-second response target remains under monitoring.
The receptionist now has more freedom to respond naturally during bookings, refund requests and greetings. Questions about prices, service differences and what is included can be answered before returning to the details needed for your request.
If a service selection is unclear, the receptionist is guided to clarify it instead of repeating the same menu. Booking checks and verification requirements still apply.
If a spoken time contains consecutive morning and afternoon descriptions, the receptionist now uses your final correction when checking availability. For example, one o’clock followed by “in the morning in the afternoon” is checked as 1 pm.
When you say not to book anything and then say goodbye, the receptionist now closes the call instead of continuing to ask for booking details. Questions about availability still receive an answer.
Our company page now shows SIMCOAI LTD’s registered office address alongside our company number and registration details, making procurement checks and formal correspondence easier.
Active calls can now finish during routine service updates. If a calling connection is interrupted unexpectedly, eligible calls can continue using fallback calling instead of ending immediately. Booking conversations also recognise distinctive package names such as “premium” without asking you to repeat the full name, while still checking when a choice is ambiguous.
Current and experimental calling now name your configured services when a caller asks about booking options. Experimental calls also pass caller recognition details through correctly, retain earlier caller details across interruptions and the opening notice, and use shorter reply context and a more responsive turn-ending setting. Brief noise while recognition finishes no longer discards the waiting reply. Simple greetings and explicit service-option questions avoid an extra response-model step. Ordinary availability answers now come directly from the checked diary without an extra response-model step, and a final goodbye after declining a booking ends the conversation. Hermes and Athena are temporarily limited to developer accounts while call quality is tested. The public realtime demo is paused; current Call Studio calling remains available.
Accounts set up with a custom free trial can move to their chosen paid plan afterwards without starting another introductory trial. The original trial keeps its agreed end date.
Hermes and Athena now use the same business conversation and request handling as current calling, including caller recognition and verification rules. Brief noises are filtered before interrupting replies. Experimental labels and the calling guide now explain the remaining reliability limits and how to switch back. Appointment changes, cancellations and refund requests still follow your business approval rules.
Experimental calling now checks the diary again when you ask for later times or a specific appointment, and speaks times in the business’s local time. Asking to pose a question no longer starts a booking conversation. Verified greetings are reused to reduce the delay at the start of repeat calls, while the recording notice still finishes before interruptions are allowed. Caller wait time now starts after the receptionist finishes speaking. The browser demo also handles delayed interruptions more reliably. Live tests now let you choose the receptionist to use, including its individual calling settings. Spoken appointment times such as “1 p.m.” are handled more reliably, and longer answers have more room to play.
Experimental phone calls now finish the short greeting and recording notice before allowing interruptions. Anything you say during the opening is kept for the receptionist to answer afterwards. Normal replies remain interruptible. The browser demo also handles interruptions more reliably when a spoken reply is starting.
The experimental realtime demo now filters brief clicks and keyboard taps before they can interrupt the receptionist. Your green speaking indicator appears when your speech is detected, and the receptionist’s indicator stays steadier during replies. Interrupted replies no longer restart from late audio, and you can cancel while a demo is connecting. Natural speech interruptions remain available.
Our major launch and feature articles now include fuller explanations, before-and-after comparisons and practical guidance. Read what changed, how it affects your business and which limits or setup steps matter, while the news list keeps its short summaries.
The browser receptionist demo now uses SIMCOAI Athena 1 for direct realtime speech, with natural interruptions, spoken replies and a live transcript. A browser connection issue has also been fixed so the demo can connect under the site’s security settings. Clearer microphone and speaker controls, suggested conversation starters and reconnect messages make it easier to try. SIMCOAI Hermes 1 and Athena 1 are available to select in Call Studio on eligible accounts; both remain experimental and use your existing allowances. The free browser demo keeps its turn and time limits and does not create real requests.
The speech-to-speech preview now has clearer model cards, an easier-to-use trailer and a simpler explanation of pilot access. Find it from the homepage announcement or the featured headline on News. The announcement includes pause and navigation controls and respects reduced-motion preferences. Live use still requires pilot approval.
Feature and setup lists now use simple green checkmarks, with clearer alignment beside the text and less visual clutter.
News articles now have a clearer heading, neatly aligned text and more comfortable spacing on desktop and mobile. Update icons keep their shape, and links to other updates are easier to spot.
SIMCOAI Vis 1.1 is our new high-end model for detailed policy questions, complex refunds, setup advice and multi-step work. It upgrades the premium model in AI Models, so existing Vis selections now use version 1.1. Each answer continues to use two premium usage units, within your plan allowance and spending controls.
Talk to your receptionist, customer callbacks, live call takeovers and browser support calls now have an alternate audio route when your network blocks a direct connection. Failed test calls keep their connection message visible so you can see why the call ended and retry.
Search results now appear above the documentation page and can be selected on desktop and mobile. Press Enter to open the first match, or use the arrow keys to choose another result. Links containing a search query also display their results automatically.
Voice previews and generated speech now read AI as two separate letters, making the pronunciation clearer and more natural. This also applies when AI appears in a longer sentence. Written text continues to use the familiar spelling.
Phone profiles now include two experimental calling choices: SIMCOAI Hermes 1 (Mini) and SIMCOAI Athena 1 (Full). Both are designed to listen and speak directly, with a different native voice, while keeping bookings, verification and transfers.
Bookings, verification, callbacks and human transfers continue to follow your business rules. Sensitive actions need their usual checks, and a refund request is not a completed refund. Call and AI allowances apply to actual native calling use.
You can save a preference now. Your current calling mode stays active until your line is approved for the pilot. We are validating response speed and booking accuracy before enabling live use; faster replies are not yet a verified result.
Watch the 36-second trailer with original music and read the setup guide.
Receptionist calls using Cura 1, Sermo 1 or Mens 1 now use our current calling engine. We corrected a response deadline that could cut off ordinary answers and cause repeated generic questions. If an answer cannot arrive in time, the receptionist now explains the interruption instead of asking for a “key detail for the team” or restarting your enquiry.
We are monitoring the correction. See calling service status.
Polite requests such as “Can you hang up, please?” now end the call with a goodbye, while questions about a booking keep the conversation open. Receptionists respond sooner to unusual enquiries and redirect unrelated requests without waiting for a generated answer. Stronger boundaries prevent requests to change the assistant’s role, reveal private information or bypass verification. The browser demo also stops listening when you ask to finish, lets the goodbye play and offers a fresh call.
SIMCOAI Vox Clara 1.5 brings responsive speech to browser demos and compatible live lines, while Vox Magna 1.5 offers richer narration and greetings on Pro or with SIMCOAI Voices. Auditus 1.5 uses our current recognition model for spoken enquiries and recorded audio. Prices are read as pounds and pence, with clearer pronunciation of SIMCOAI and common service words. Call Studio shows the models your current call setup supports; existing lines keep their compatible voice until upgraded.
The AI model cards on our features page now show each full model name clearly and include Cura 1, so all four options described there are visible together.
We corrected our website and product summaries to explain where your sign-in credentials are handled. Our separate SIMCOAI sign-in service manages them; the dashboard does not store your password.
Choosing a model is clearer when every page uses the same names. Our AI model guide, technology page and earlier updates now name Cura 1, Sermo 1, Mens 1 and Vis 1.1 consistently. Viva 1 remains experimental.
Voice and speech names are aligned too, so you can compare your options without translating older labels. See the AI model guide or explore the technology page.
We refreshed the photos on our home, contact and pricing pages with licensed images. The pictures are illustrative, and our product screens continue to show the actual SIMCOAI experience.
Our page footers now show a clear SIMCOAI LTD copyright notice. It identifies the company behind our original website content and software while respecting the licences of third-party components we use.
Photos sent through a SIMCOAI proof upload link are now encrypted when stored. The change also covers photos already uploaded through those links. You can continue to send and view proof photos as usual; no action is needed.
The browser demo now starts listening sooner so short greetings are less likely to be clipped, and each new demo session can use a different receptionist voice. During a full phone call, the receptionist can offer a text link if a name or email address is hard to hear. You can type your details instead of spelling them aloud, and take time to finish before continuing. Protected requests still require verification.
The icons across the pricing page now display fully and sit correctly in their badges, making plans easier to scan and compare.
The browser receptionist demo now responds to what you say in a more natural conversation. It remembers earlier answers and asks for the next useful detail without repeatedly reading a menu. The opening is shorter, replies start sooner, and your words appear in the transcript as you speak on supported browsers. The call screen now keeps the conversation and controls easier to see on phones and desktops. It remains a demo: no real booking, refund or callback is sent.
We expanded our Terms and nine related policies with clearer details about account authority, data protection, AI review, calls, billing, refunds and support. Please review and accept the updated policies in your account to keep using dashboard features. If you choose not to accept a material change, you can cancel and request a pro-rata refund for unused prepaid service.
We fixed a gap that could let account API keys access SIMCOAI before the account owner had accepted the current policies. Access now waits for that acceptance, including read-only keys. Terms confirmation also checks your choices more carefully, and account settings follow the same access rules.
Security checks on SIMCOAI forms now stop promptly if the checking service is unavailable, so you can try again without waiting indefinitely. We have also strengthened the protection around contact messages and how traffic signals are checked.
When you use staff scheduling, the receptionist now checks how many people can take an appointment before offering another place at the same time. This also accounts for bookings that have not yet been assigned to a team member, so a timetable limit cannot offer more appointments than your available staff can cover.
The receptionist now prepares website endings such as .co.uk and phone numbers more clearly for speech, including when an answer arrives in small pieces.
When callers ask about your team, the AI receives relevant active staff names, roles and linked services. Private staff contact details stay out of those answers, and appointment availability still comes from your booking timetable. A greeting no longer brings in recent customer records or the booking timetable.
Random voice selection keeps your chosen voice model. Browser call tests now use that same model choice, and speech generation no longer silently switches to a different model when a request is rejected.
Asking to escalate a refund query now starts the team-review process even when the refund is already recorded. Verification follows the review request instead of repeatedly returning to the closed refund. Simple greetings and requests for an order number also answer sooner, and short replies keep their complete sentences.
Links using www now take you to the same SIMCOAI address used throughout our website. Older documentation homepage links also take you straight to the current homepage. This helps search engines recognise a single address for each page and keeps shared links consistent.
Usage and statistics requests now fetch fresh data after CSV or document uploads. An older reply can no longer restore previous cached figures, including replies completed while an upload was still in progress. Upload failures also leave the dashboard ready to request fresh data.
Premium AI replies now prepare their allowance checks together, reducing avoidable waiting before an answer starts. Both usage allowances still use fresh information for every request, with the existing credit and pay-as-you-go rules. If usage cannot be checked, the reply still stops safely.
Quickly closing and reopening the notification, account or display-settings menu now keeps the reopened menu visible. An earlier animation can no longer hide it or bring back a panel you have closed. Menu toggles follow your latest action during both standard and calm motion.
Delayed notification replies can no longer restore an old unread badge after you mark notifications read. Older lists and errors also cannot replace a newer notification list, and the badge follows the latest count request when list loading and count checks overlap. Repeated clicks on one notification now share a single pending read action, keeping other unread notifications counted correctly. A single read finishing after “mark all read” also cannot reduce the count of notifications that arrived later. Failed read actions remain available to retry.
Refreshing dashboard records now requests fresh data. If two loads overlap, an older reply or error cannot replace the newer result. Replies started before a dashboard save also cannot restore outdated records, and an older load finishing no longer makes a newer load appear complete. This applies to records loaded by the shared dashboard loader, including orders, bookings and refunds. Workflow refreshes also update lists and counts in place, preserving an unfinished order, booking, refund or escalation form. A refresh finishing after you leave the page no longer rebuilds your new view. A workflow save finishing in the background also keeps a newer record editor open. It refreshes the records from the page where the save began and preserves a different page you have opened meanwhile. CSV imports now follow the same rule: completing an import updates its original records without replacing a page or unfinished form you opened while it was uploading. Deleting a record or completing a workflow action now also refreshes its original page safely, including when an action has already been handled.
Customer imports and new contact records now require a successful phone-sharing check before assigning a number. If that check is temporarily unavailable, the affected import row is skipped with a clear retry message. Normal shared-phone handling is preserved.
Customer import reports now explain skipped rows with clear messages. Contact conflicts remain actionable, while unexpected failures ask you to try again later without showing internal technical details. Imports also reuse your custom-field settings throughout each file, reducing repeated lookups while keeping field validation and existing customer details intact. Re-importing equivalent custom-field values now keeps rows unchanged, and rejected choices or invalid statuses no longer count as updates. Imports also spend less time preparing updates for your connected integrations, reducing the wait for the final report while preserving existing notification handling.
Files exceeding an upload's size limit now show a clear message asking you to choose a smaller file, instead of reporting a server error. Rejected customer import files stop before any customer rows are processed.
Statistics summary amounts, call minutes and rates now cover every matching record in the selected period, even when the detail list is limited. Previous-period comparisons use complete totals too. Charts and breakdowns continue to identify when they use a limited detail window. Statistics also refresh after dashboard saves, and delayed replies from before a save cannot replace the newer results.
Hourly statistics now include every hour in your selected period, including quiet hours near the end of longer ranges. This fixes gaps that could appear after the first 500 hours in charts and statistics exports. Large statistics views also prepare their exact values faster, while keeping the same number and currency formatting.
We fixed an edge case where parts of an AI reply could be missed when a response arrived in several parts. Replies now retain that text while continuing to stop promptly when a caller interrupts or the call ends. Short completed confirmations and questions are also retained after a connection problem, helping avoid repeating an answer that has already begun. Replies retained after a connection problem now finish cleanly as streamed replies too. Recovery also recognises common name titles, so an unfinished phrase ending at a title such as “Dr.” is no longer mistaken for a completed sentence. Reply time limits now also hold when delivery stalls, helping timed-out or interrupted turns stop promptly. Cancellation also covers replies that arrive all at once and recovery attempts, so superseded turns stop without waiting for their full time limit. We also prevent an outdated reply from being finished or corrected after a newer caller turn has begun. Interrupted replies also stay cancelled when an interruption coincides with the reply time limit, avoiding recovery of a reply the caller has already moved past. Automatic compatibility retries also share the original reply time limit, including replies that arrive all at once, so a retry cannot extend the total wait for an answer. Replies also stop cleanly when an error arrives partway through, keeping text already delivered available for recovery and preventing extra text after the failure. Errors arriving before any reply text are recognised as failures rather than empty successful replies. This also covers an additional case that previously let a failed answer appear successful.
Quickly clicking the same dashboard button again now waits for its current action to finish, helping prevent duplicate submissions. Once the action completes or reports an error, the button is ready to use again.
A customer's recent calls now remain visible even when your business has handled many newer calls from other people. Customer records show their newest 25 matching calls, with the same matching for local, international and formatted phone numbers.
We fixed an issue where customer spreadsheet downloads could stop after the first 500 matching records. Exports now include the complete matching list, including larger lists and filtered results. If a download cannot be completed, it fails rather than returning an incomplete spreadsheet as a success.
Booking requests written as day/month/year now keep their requested date when the time is interpreted. If a numeric date does not exist, such as 31 April, your receptionist asks you to repeat it instead of offering or confirming a different day. Named dates such as 30 October 2027 also retain the year you supplied. Impossible named dates ask for clarification, and valid leap-year dates remain supported.
If SIMCOAI cannot check whether a booking, refund or escalation already exists, it now stops that attempt instead of treating the failed check as an empty result. This reduces the risk of creating a duplicate during a temporary service problem. You can retry once the check is available again.
If you search again while an earlier customer search is still loading, the earlier result can no longer replace your latest results or customer count. Errors from superseded searches also stop appearing after a newer search succeeds. The customer summary count now updates alongside the list when you search or refresh. Opening customer details also keeps your latest selection: delayed replies cannot replace it or reopen details after you leave, go back or edit. Customer details also load their independent history sections together, reducing the wait for the full record. A save finishing in the background also keeps a newer customer editor open, protecting the draft you are currently working on. Adding a customer now also preserves a new draft typed while the request is pending, and delayed completion keeps your current editor or page in place. Delayed customer refresh, search and clear-search actions also leave a newer page or editor untouched. Adding a custom field now keeps unsaved customer details and any newer field draft in place, while making the new field available immediately. Removing a custom field also preserves other unsaved customer details, and your allowance and Add field controls update immediately as slots fill or become available. A customer deletion finishing in the background also keeps a newer page or editor intact. Import completion preserves a newer file selection and your current view, keeps the report available when you return, and prevents an older upload from replacing the latest report. Completed imports also show their report if the customer list cannot refresh, with a clear prompt to refresh the list. Errors from an older upload no longer interrupt a newer import or another page.
If you cannot provide an order number, giving contact details now moves the refund conversation forward instead of asking for those details again. We also made record-ownership guidance consistent across AI replies: quoting a reference number alone does not establish that a record belongs to the caller.
Dashboard requests now reuse account information already verified during that same request, avoiding a duplicate check. Every new request still checks the current account identity and suspension status.
When the same account requests identical statistics at the same time, SIMCOAI now prepares the result once for those requests. This reduces duplicate work during overlapping refreshes. Each later refresh still loads current information.
We fixed a timing issue where a slower dashboard read started before a save could replace newer cached information afterward. Saving now prevents those earlier reads from restoring outdated information for later page loads.
We fixed an edge case where the end of an earlier AI reply could still be delivered after a caller interrupted or the call ended. Interrupted replies now stop before any remaining words are delivered, including replies that arrive together while the caller takes over.
We have added another layer of connection protection to SIMCOAI. It blocks unsolicited access to services that do not need public connections and limits repeated attempts to connect to administration services. Your dashboard and calling services continue to work as usual.
If a dashboard connection drops while a save response is arriving, the saving notice now clears and a connection error is shown so you can check your changes before trying again. AI responses now release their connection when they finish or fail, and respect the overall response deadline even when it is shorter than the wait for the next part of a reply.
Pricing now explains Cura 1, Sermo 1, Mens 1 and Vis 1.1 alongside standard and premium usage. Our model guide and AI policy clarify what the names mean and why Viva 1 remains experimental. Refreshing AI Models keeps the current catalogue visible, and legal contents links reveal sections hidden by search. Fixed model choices supplied using catalogue names or keys now retain the selected configuration instead of switching to automatic routing.
Press Ctrl+Z (or Command+Z on Mac) to undo a recent unsaved switch or dropdown change in the dashboard. Text fields continue to use your browser’s normal undo.
Saving your booking timetable now keeps the page and calendar in place. Your saved services and opening hours update without the screen flashing or jumping, and the save confirmation appears beside the timetable.
When you have not enabled staff scheduling, booking calls now use your business timetable, including available weekend times. An exact service name is matched before similar names. If a caller cannot remember an order number, the assistant asks for the email or phone on that order instead of assuming it has already been given.
Phone replies now start sooner. SIMCOAI reads the current conversation alongside the details it needs, and routine account checks no longer hold up each answer. When a caller asks for your complete published opening hours, the assistant answers directly from your settings.
Your AI Models page now explains when to use Cura, Sermo, Mens and Vis, and names every voice and speech option. SIMCOAI Vocatio is our name for calling. You can choose a model yourself or let SIMCOAI pick for each request. Growth includes 50 premium usage units for Vis each month, Pro includes 250, and Premium AI Models adds 1,000 more.
SIMCOAI Sermo 1 now helps answer live calls and support questions. It is tuned to start replying quickly while keeping answers clear and useful.
We now make an encrypted local backup of core workspace data every hour and keep copies for about 30 days. While a backup runs, saving settings waits and continues automatically when it finishes. Backups are currently local; separate-site backups are planned.
Open a booking from your calendar and its details now appear without shifting the page away from the date and time you were viewing. You can close the details and carry on from the same place.
We corrected the layout of several paragraphs in the bookings and account security guides, making both guides easier to read.
When someone calls to book, SIMCOAI now offers available times and lets them choose one. This fixes a problem that could stop the booking conversation before any times were offered.
Switch on staff scheduling and set each person’s hours. SIMCOAI assigns someone available automatically when the caller has no preference. A named request is checked against that person’s availability. Switch it off whenever you want to use shared booking capacity again.
Key guidance is easier to reach. The homepage now points directly to setup help, common questions and privacy information. You can email SIMCOAI from the contact line in the Privacy Policy and Terms.
Dashboard actions are easier to read and tap. Button labels have more room, and groups of actions move onto a new line when space is tight.
The email designer now keeps your place while you work. Add, move or duplicate content blocks without resetting the text you are editing. Switch between the visual canvas and HTML while the live preview stays visible.
The WhatsApp message window stayed open when you pressed Escape. Escape now closes it, just like other dashboard pop-ups, so you can return to the page underneath.
If a caller corrected an email address or callback number, an older saved contact detail could still take priority when the request was recorded. The detail spoken on the current turn now takes priority for callbacks and verification. The assistant still reads verification destinations back so callers can correct a misheard address.
Spoken answers to an open question on the support line could fail to reach the assistant. We updated the listening step to use a supported pause setting. The menu still accepts speech and keypad choices, and callers can ask for a person at any point.
A busy call history could push a call still in progress out of Live Calls. Active calls now stay at the top. The list keeps the newest recent calls beneath them and drops older entries when it is full.
Refreshing Your phone numbers could flash the whole dashboard, and Release number was hidden at the far edge of a scrolling table. Number cards now show the release action beside the number. Refresh updates the number details in place, and other same-page dashboard updates keep unchanged sections mounted.
The phone number guide now explains manual release, downgrades and what happens when a subscription ends.
Calling a customer back from an escalation or record now opens the live Call Studio room. Staff can speak hands-free, mute and hang up, using only an active business number assigned to their account. Monthly callback allowances appear on the pricing page and are checked when a call starts.
You can also release an assigned number from Your phone numbers after confirming it. When a plan ends or its number allowance drops, SIMCOAI releases numbers that no longer fit the plan; a first failed payment alone does not release them. Email Studio preferences now save without repainting the whole page, and their checkboxes display correctly.
The homepage demo looked like a message recorder and the site itself blocked microphone permission. It now opens as a two-person, hands-free call room with automatic turn detection, interruptions, a mute control, timer, speaking indicators and a secondary live transcript. The microphone policy and the anonymous audio route have both been corrected.
Public call details now use SIMCOAI product names throughout. Supplier engine names no longer appear in the demo configuration, audio responses or signed browser session. The public allowance is enforced against a verified network address plus a stable browser identifier, so a forged forwarding header cannot reset it.
Some phone calls said “One moment” and then cut that phrase off when the real answer arrived. That extra phrase has been removed completely rather than used to disguise response time, so callers now hear one clean answer.
We also shortened the first booking step: when the receptionist only needs to ask which service the caller wants, it now asks directly instead of waiting for an AI rewrite. Open questions, availability checks and booking completion still use the full call logic.
Changing between normal and light mode no longer rebuilds the dashboard navigation, reloads its icons or adds a full-page transition layer. The colour change now happens immediately regardless of how large the current page is.
The live call room, mobile navigation, integration flow, charts and newer editor panels now follow light mode instead of retaining dark backgrounds and controls.
The documentation now goes beyond setup steps into production launch checks, knowledge governance, voice testing, workflow ownership, reliable integrations and incident triage. The added runbooks explain what to verify, what evidence to keep and how to recover safely when something goes wrong.
Documentation search now ranks more of the words inside each guide, understands common terms such as MFA and OTP, and opens the first result when you type a query and press Enter.
Moving between tabs within a dashboard section now has a short, subtle fade and lift instead of changing abruptly. Switching themes or light mode is smoother too, while doing much less work on large pages.
Reduced-motion preferences are still respected, and no transition delays the page from becoming usable.
SIMCOAI can now send live bookings into your Fresha calendar as blocked time, with no extra SIMCOAI add-on charge. Copy the private calendar link from Integrations, add it to Fresha as an external ICS calendar, and Fresha keeps the availability up to date.
The connection uses Fresha’s supported calendar import. It is one-way from SIMCOAI to Fresha, so it never depends on an unofficial or private Fresha API.
New booking and escalation notifications had their title pushed further right than the details underneath. The unread marker now has its own space, leaving the title, description and time on one clean edge.
Choosing another call in Live Calls now uses a short, calm transition while its transcript and controls change. The call list, page position and transcript position stay where you left them, so it is clear what changed without the dashboard flashing or jumping.
Customers who prefer reduced motion see the new call immediately without the transition.
SIMCOAI links now use a purpose-built sharing image with the real SIMCOAI logo, clearer text and the right wide shape for messaging and social apps. Page titles and descriptions remain specific to the link you share.
We also connected the main feature descriptions to their detailed pages, making it easier for visitors and search engines to move between related information.
If a call connection faltered after the receptionist had already started answering, it could restart the answer from the beginning. Calls now keep a complete sentence that was already spoken instead of starting a second answer.
This also avoids using another AI request when the caller has already received a useful response. Short or cut-off fragments are still discarded, and interrupted or ended turns stay cancelled.
You no longer need to know when to hard-refresh the dashboard, website or help pages after we release a change. An open page now checks for updates automatically and shows a clear “Refresh now” message when a newer version is ready.
The check also runs when you return to an older tab, and page updates are detected automatically rather than relying on somebody remembering to publish a separate refresh signal.
Changing a dashboard widget, editing an AI instruction, saving Call Studio settings or reordering two-step verification methods could suddenly move the page by hundreds of pixels. Those small updates now hold your place instead of making the surrounding page jump.
We also completed an interaction sweep across all 51 dashboard sections and 345 safe controls, including the sections that an earlier run could not reach.
Browser calls now open in a dedicated voice room. See speaking activity, mute your microphone or sound, choose audio devices, minimise the room or use fullscreen. Human takeover stops AI listening and replies once you connect.
We fixed browser error handling that could end an otherwise open call, stale Live Calls requests and transcript refreshes that replaced controls. Sidebar tabs also stay the same size when pressed.
The voice picker now shows the available speaking voice names. Phone-number profiles can use your saved Call Studio voice, including rotation, instead of silently overriding it. Live call engine labels now match the supported engine actually used.
Live Calls now connects your browser microphone and speakers directly to the caller. The caller stays with the receptionist until you connect. After takeover, AI listening, transcription and replies stop. Use mute, keep talking while navigating the dashboard, and end the call for both. Ordinary call charges continue; AI usage already incurred remains counted.
We also fixed delayed suspension checks and Statistics refresh races, stale results and incomplete breakdown percentages. Statistics now shows previous-period totals, UTC dates and an exact-values table, with clearer light-mode contrast.
Our live-call guide, pricing explanation and relevant policies now describe handoff availability, recording and usage.
Your account being suspended, a payment failing, or your free trial ending can now reach you by text, not just email. It's optional and off by default — verify a phone number on the Security page, then switch it on. Everyday activity still only ever goes to email; this is reserved for the handful of events where missing it could genuinely cost you.
If you have more than one member of staff, the booking calendar now has a "By staff" view alongside the usual week view — showing everyone's day in their own column at a glance, instead of switching one person at a time. Click any booking to open its full details, and use the day arrows or "Today" to move around. Businesses with one member of staff, or none, see no change.
Call Studio's test button used to record what you said, send it off, then play back one reply at a time — closer to a chat box than a phone call. It now places a genuine, two-way call straight from your browser to your actual receptionist, using your real greeting, voice, opening hours and booking diary. You can talk over it and it can talk over you, exactly like a real caller would experience. A simple "who's talking" display shows you and your receptionist as the call happens. Because it's a real call, it uses the same call minutes and voice allowance a genuine customer call would.
Add staff members with their own hours — including part-time — free on your plan. Callers can ask for someone specific by name on services you allow it for, the AI only offers times that person is actually free for, and your calendar can switch between "all staff" and one person at a time. A solo business sees nothing different unless staff are added.
Call Studio showed a voice model as part of your plan, but there was no way to actually pick between them. Growth, Pro, Enterprise and SIMCOAI Voices add-on accounts can now choose from four live-call voice models directly in Call Studio — SIMCOAI Vox Prima 1, Rapid, Natural and Classic — each trading off speed, cost and warmth differently. Random voice rotation was also checked over and a rare case where the readiness panel could show a voice picked for a different account has been fixed.
"Take the tour" used to open a page and describe it in a floating card, leaving you to find the actual setting yourself. Every step now scrolls to and highlights the real control — the Display settings icon, the greeting box in Call Studio, your booking timetable — with the page dimmed around it, and moves you there itself rather than asking you to go looking.
Switching between Simple view and the full dashboard, or between light and dark, used to snap instantly with no transition. It now cross-fades smoothly. Buttons, toggles and alerts across the dashboard and sign-in page can also play a short, soft confirmation tone — on by default, with a one-click toggle in Display settings (dashboard) or the small speaker icon (sign-in page). Anyone with reduced-motion preferences set on their device automatically gets the instant version with no animation.
If a way of signing in presented a verified email address matching an existing SIMCOAI account, it used to be attached to that account straight away, with no confirmation. That is fixed: linking now only happens when you start it yourself, signed in as the account you want to add it to.
There's a new Connected accounts tab on the Security page for this. It shows which providers can sign you in today, lets you add another one, and lets you remove one — you always keep at least one way in, so the last one can't be disconnected by mistake. Adding or removing a connected account asks you to re-confirm your password or two-step method first, the same as every other change on that page.
GitHub joins Google as a way to sign in, from the same sign-in page. Press "Sign in with GitHub", approve access on GitHub, and you're in — or add it later from Security → Connected accounts if you'd rather keep using a password for now.
The dedicated SIMCOAI Zapier app previously asked you to create an API key in your dashboard and paste it into Zapier by hand. It now uses the same "Connect an Account" flow you already know from connecting Google or Slack to other apps: press Connect, sign in to SIMCOAI if you aren't already, and approve a plain-English list of what Zapier may access — orders, refunds, bookings, escalations and customers. There is nothing to copy, nothing to lose the only time it's shown, and you can disconnect it any time from Account → API Keys.
If you'd rather scope access more narrowly than the dedicated app's connection grants, creating your own API key and using Zapier's built-in Webhooks app is still there as an option. See how both methods work
Until now, the SIMCOAI Zapier app could send data out of SIMCOAI, and only create or update orders and customers from another app. It can now log a booking, a refund request or an escalation from any app that connects to Zapier — a call centre tool raising an escalation, a form builder logging a booking request, an accounting app flagging a refund.
A single "Update a Record" action replaces needing four separate ones. Pick the record type, paste in an ID from an earlier step in your Zap, and set a new status or notes — the same action covers orders, refunds, bookings and escalations, which is what makes setting up a Zap simpler than before.
All six actions are tested against the live SIMCOAI API. See the full list of triggers and actions
Two changes to how SIMCOAI stores its own credentials and the secrets it holds on your behalf — a webhook signing secret, a connected AI provider key. Both are now encrypted at rest with ChaCha20-Poly1305, a published, independently reviewed authenticated encryption standard (RFC 8439) also used by Google, Apple and Cloudflare in their own production systems, using full 256-bit keys throughout. Every stored secret carries an authentication tag: if it is altered by even one bit, decryption is refused outright rather than returning a tampered value, and a secret held on your behalf is individually bound to your account, so a copy of one record cannot be read against another.
SIMCOAI's own operational credentials — the keys we use to reach our payment, calling, messaging and AI providers — moved out of a plain configuration file and into a dedicated, self-hosted secrets manager running on our own infrastructure, decrypted only in memory at boot and never written to disk as plain text. Nothing about how you use SIMCOAI changes. How we protect your data
Our support line can now verify who you are, the same way our AI receptionist verifies your callers before it discusses a booking or a refund. Ask something like "what plan am I on" or "is my subscription active" and the line asks for the email on your account, emails a real six-digit code to it, and asks you to read it back. Get it right and, for that call only, it can tell you your plan, whether it is active, and whether your account is suspended — nothing is changed, only read back to you.
It answers exactly the same way whether or not that address has an account with us, so it can never be used to work out who our customers are, and a wrong code is refused however many times it is tried — five wrong attempts and it stops trying the code and offers you a person instead. A code expires after ten minutes even if it is correct after that. Everything the line will still never do — set a new password, turn two-step verification off, remove a device, change your email, or unlock an account — is unchanged; those still go to a person who verifies you a different way. What our support line can and can’t do
The Zapier setup guide undercounted what SIMCOAI could do - it listed nine triggers when SIMCOAI has always published sixteen (every stage of a booking, order, refund, escalation and customer), and its steps implied a SIMCOAI app already existed in Zapier’s own picker. Neither was true. The Integrations page in your dashboard now shows the real sixteen triggers and the connection method that works today - Zapier’s own built-in Webhooks app, no code and no waiting on a directory listing. You can also log an order, add or update a customer, or search for one from a Zap, not just send data out of SIMCOAI.
You can now send what SIMCOAI takes on the phone into any of Zapier’s apps, without writing anything. Bookings into your calendar, escalations into Slack, new customers into your mailing list, refund requests to whoever approves them. Nine triggers, each firing the moment the record changes rather than on a delay. Setup is an API key from your dashboard pasted into Zapier. For developers there is also a CRM bridge that returns a customer and everything attached to them in one request, with incremental sync. How to connect Zapier
The dashboard now has a simple view. It hides the pages a new business does not need on day one — model routing, test labs, the API keys screen — and leaves the ones that decide whether your phone gets answered properly. Nothing is switched off and nothing stops working: it is hidden, not locked, and one button in the top bar shows everything again. New accounts start in the simple view; if you already have an account, nothing about your dashboard has changed.
And the guided tour now starts by itself the first time somebody opens the dashboard — including a team member signing in for the first time, who previously never saw it if they were on a shared computer. It has been rewritten from scratch: nine steps in the order a business actually needs them, each with one thing to do and how long it takes, and it remembers where you got to even if you switch machines. You can start it again whenever you like from the Command Centre.
Your receptionist also sounds less like a machine. We measured sixty real replies: it was using the caller’s name in ten of them and opening with “I can help” or “Of course”. A receptionist says your name once, not every sentence. It now leads with the answer, uses contractions, and reads a list of times aloud properly — “eight o’clock, nine o’clock or ten o’clock” rather than “8, 9 or 10 am”. Hear it in Call Studio
Ring +44 7576 569444 and the line can send a password reset link to an email address you give it. Until today it could only tell you where to find the reset yourself. The link goes to the mailbox and is useless to anybody who does not already read it, which is why it needs no further check — it gives you nothing the reset link on our sign-in page does not already give any visitor. The line answers the same way whether or not that address has an account with us, so it cannot be used to work out who our customers are.
Nobody at SIMCOAI can read your password. It is held by our sign-in provider as a one-way scramble, and there is no screen, export or support tool anywhere that returns it — not a permission we could grant ourselves if we wanted to. So if you ask us what your password is, the honest answer is that there is nothing to look up, and the line says so rather than pretending to check.
And there is a short list of things it will never do, however convincing the caller. It will not set a new password, turn two-step verification off, remove a passkey or security key, change the email address on an account, or unlock one. Those are exactly what somebody impersonating you would ring up and ask for, so they go to a person who verifies who you are first. That is slower, and it is the same slowness that stops somebody else doing it to your account. Companies far larger than us have been taken apart through a helpful support desk rather than a cracked password.
We will never ask you for a password, a one-time code, a passkey approval you did not start, remote access to your computer, or card details — on our line or on any call we make to you. If somebody does, it is not us: end the call and ring the number above. Your Security page now lists this too, next to the settings it applies to. How account security works
We have withdrawn the emailed sign-in code. It let anyone who could read your inbox sign in without ever knowing your password — and a password reset arrives in that same inbox, so two things that were supposed to be independent were really one. It is switched off in the dashboard, removed from the sign-in page, and closed at the sign-in service itself, so it cannot be reached by any route.
What you use instead: your email address and password, a passkey, or a security key. Passkeys and security keys are the only things that can sign you in without a password, because they never leave your device and cannot be phished or copied out of an inbox. Signing in with Google is unchanged.
If you were relying on the emailed code and do not remember your password, use the reset link on the sign-in page — it still works exactly as before. Go to sign in
Until today it did not. Opening the dashboard on a phone showed a card telling you SIMCOAI works best on desktop, with links to the website and the docs — you could not reach your own account at all.
There is now a simple version built for a phone, carrying the things you would actually want while you are out: your overview and statistics, Call Studio to hear how your receptionist sounds, your call log, your diary, your numbers, your security settings, and how to contact us. It has its own bar along the bottom to move between them.
Everything else is one tap away. Pages built for a desktop — orders, refunds, the AI editors, billing — say so and offer to switch this phone to the full dashboard, and there is a control to come back to the simple view whenever you want. Nothing about the desktop dashboard has changed. Open your dashboard
The next time you open your dashboard you will be asked to accept the current SIMCOAI policies. It takes one screen: every policy is listed with a link so you can read it there, and accepting unlocks the dashboard again. We have done all ten together so you are only asked once rather than each time a policy is amended.
Nothing has been taken away from you. The changes since you last accepted are corrections and additional disclosure — who processes your data by name, what happens when you ring our support line, that we hold no password of yours — plus the new Refund Policy. If you would rather not accept, you can cancel and we will refund the unused part of your period, which is what our terms have always said and is now worked out and paid automatically.
Eight of the nine policy pages showed a “Last updated” date earlier than the day their wording actually last changed, some by more than a month. That date is the only thing on a policy telling you whether you are reading the version you agreed to, so it should never be wrong. Every page now carries its real date, and a check runs against the page history so it cannot drift again.
Nothing about how the service behaves has changed, and no calls, bookings or records are affected.
There is now a single page saying when we refund and when we do not. Until today that was spread across two clauses of the Terms and one of the Billing and Tax Policy, so you had to already know where to look. It is at Refund Policy and it is linked from the footer of every page.
Nothing you are entitled to has changed. The policy states the position that already followed from the terms you accepted, in one place and in plain English — including the parts that are not in your favour. SIMCOAI is sold business to business, so the Consumer Rights Act and the 14-day right to cancel a distance contract do not apply, and cancelling part way through a period you have paid for is not refunded. We would rather tell you that plainly than have you find out.
What has changed is that we now do the arithmetic and pay it. Our terms have always promised a pro-rata refund if we withdraw the service, retire a plan you pay for, change the terms in a way you decline, or cannot supply for a prolonged period — and there was no system behind that promise. There is now: the unused part of your period is calculated and returned to the card that was charged, without you having to ask or work out the figure. A charge that was never owed goes back in full.
The calculation uses what you were actually charged rather than your plan’s list price, measures real elapsed time so a six-month or annual term is not rounded, and rounds any fraction of a penny in your favour. Refunds we have issued appear on the Billing page of your dashboard with a credit note reference.
Sign-in by text is not available, and one update here went on saying it was. We withdrew it on 15 August because it could not sign anybody in, and we said so in the 13 August update — but only four paragraphs down, while that update’s headline went on promising it for three days. The headline now describes what actually changed, and the correction is still there in full. Signing in by email, by an emailed code, with Google, with a password or with a passkey were never affected.
Two different updates about the Security page shared one address. Following a link to the newer one gave you the older one, and the newer one had no address of its own. They are now separate, with the right dates on both.
The sign-in page footer was missing our phone number for a day. We added the support line to the footer of every page on 17 August; the sign-in page is built separately and did not pick it up until the following morning. It is there now, and a check we already had is what found it.
None of this affected the service itself — calls, bookings and the dashboard were unaffected throughout. We publish corrections rather than quietly editing an update, because an update you cannot trust is worse than no update.
There is a page for them: simcoai.co.uk/technology. The AI models that answer your phone are SIMCOAI Cura 1, Sermo 1, Mens 1, Vis 1.1 and Viva 1. The voices are SIMCOAI Vox Prima 1, Vox Velox 1, Vox Clara 1, Vox Firma 1, Vox Artis 1 and Vox Magna 1. The speech engines that listen are SIMCOAI Auditus Vivus 1, Auditus Certus 1 and Auditus Communis 1. Each one says plainly what it is for, so choosing between them is a decision you can make rather than a guess.
Each name is a configuration we build and run — its own instructions, context routing, deadlines and guardrails — on top of a frontier base model. That is the part we control, which is why we can move to a better engine underneath without you having to re-choose anything or re-learn what you bought. We are not claiming to have trained a model from scratch, and we say so on the page.
The dashboard stopped showing you version strings. The voice readiness panel used to read like a list of other companies’ release notes; it names SIMCOAI Speech and SIMCOAI Voice now. Your usage rows say “speech minutes” and “voice minutes” rather than naming suppliers you never chose and cannot change.
Every provider we rely on is still named in full where it matters. Our privacy policy and GDPR page now carry a table mapping each SIMCOAI name to the company that actually processes that data, because naming who handles your customers’ information is a legal requirement rather than a presentational choice.
Your Security page now shows the recent activity on your account. Every sign-in, wherever it happened — not only in this browser — with the date and time, the kind of device, the country and the address it came from. Failed attempts and password resets are listed too, so you can tell an ordinary week from one that needs looking at.
There is a Sign out everywhere button beside it. It ends every other signed-in device on your account and leaves you signed in where you are, which is what you want if you have lost a laptop or think somebody else has your password. If your account has been temporarily locked after repeated failed attempts, the page now says so and offers to clear it, instead of leaving you wondering why your password stopped working.
Two-step verification has also been added to the list of protections at the top of the page, so you can see at a glance whether it is on. Nothing about how you sign in has changed, and you do not need to do anything.
You can now add a second step to signing in, from Security in your dashboard. It means somebody who has your password still cannot get into your account. It is off unless you turn it on, and turning it off again never needs anyone’s permission but yours.
You pick the methods, and the order. Choose any of an authenticator app, your fingerprint or face, a physical security key, or a code by text — and turn off the ones you do not want offered. Whichever you put first is the one you are asked for first; the rest are there as a fallback. If you only want an authenticator app, that is the only thing you will be shown.
Recovery codes are always included and cannot be switched off. Losing your phone should not mean losing your account, so you will always be offered codes to save or print.
Turning a method off changes what you are offered when setting one up — it never stops you using something you have already set up, so you cannot accidentally lock yourself out from this screen. To stop using one for good, remove it from the same page.
A passkey remains the quickest and safest option and still works on its own. If you already use one, you are covered.
The sign-in page had no navigation and no footer. Once you reached it there was no way back to pricing, the docs, the status page or anything else without using the browser’s back button — it looked like a different site. It now carries the same header and footer as every other SIMCOAI page, built from the same source, so a link added anywhere on the site appears there too. Those links open in a new tab on purpose: a sign-in in progress is only valid once, and wandering off in the same tab would have meant starting again.
You can now sign in with a code sent to your mobile. There is a “Text me a sign-in code” option on the sign-in page. Choose it, enter your number, and the code arrives by text instead of email — useful if your email is slow or you are already on your phone.
Typing a phone number used to lead nowhere. The sign-in box invited a phone number and then asked for a password, which nobody has against a phone number, so it was a dead end. The box now asks for your email address and the code-by-text option is a separate button that works.
Correction, 17 August 2026: sign-in by text has been withdrawn. It could not sign anybody in — the code was sent and accepted, and the last step then failed, because no account had a mobile number recorded against it and there was no way to add one. Rather than leave a button that cannot work, we have removed it. Signing in by email, by an emailed code, with Google, with a password or with a passkey all work as before, and we would rather add a phone as a second step after your password than as a way in on its own — a number can be moved to another SIM, and that should never be enough to reach your account.
SIMCOAI has a support line. Ring it and you are asked to press 1 for help with your account or 2 to speak to a person. Press 1 and you reach an assistant that can talk you through signing in, resetting a password, what is on your plan and how billing works. Press 2, at the menu or at any point afterwards, and you are put through to somebody on the team.
If nobody is free, you are not left with nothing. Rather than ringing out, the line takes your number and puts you in a callback queue that a person works through, and it tells you that is what has happened. The same thing happens if the call reaches a person and they cannot pick up in time.
The line opens with a notice that you are speaking to a digital assistant and that the call may be recorded, before anything else happens. That notice is part of the platform and cannot be switched off.
It never asks for a password, a sign-in code or card details, and it will not discuss anything specific about your account, because it has no way to confirm who is calling. Anything of that kind goes to a person.
You can choose where your six-digit sign-in code goes. Email still works exactly as it did. If you would rather have it as a text message, you can now use your mobile number instead — useful if your email is slow to arrive, or if you are signing in from a phone and would rather not switch apps.
Codes are sent from SIMCOAI, through the same protections as everything else we send. The code itself is never written into our own records, there is a firm limit on how many can be sent to one number in an hour, and premium-rate and satellite ranges are refused outright — those exist to stop somebody running up a bill by asking for codes they never intend to use.
Replying to one of those texts now gets an answer pointing you at somewhere useful, and replying STOP stops them. Before this, a reply reached nothing at all.
What you buy from us is now named after what it does. Calling, Voice, Speech, Messaging, Payments, Identity and Intelligence are the parts of SIMCOAI, and the models your receptionist runs on are SIMCOAI Sermo 1, Mens 1 and Vis 1.1 — named for the choice you are actually making, which is how fast an answer comes back against how much thought goes into it.
Nothing about your service changes. This is what things are called, not what they do. The same voices, the same speech recognition and the same models are behind them.
Our legal pages still name every company that processes your data. The privacy policy, the GDPR page, the terms and the cookie policy list our sub-processors by name and always will — that is a legal requirement and the one place where naming them matters more than tidiness.
There is a new AI Instructions page in your dashboard. Your refund and booking policies say what to do when something happens. These say how you work — the things you would have to explain to a new receptionist on their first day.
“We only take MOT bookings on weekday mornings.” “Never quote a price over the phone.” “Always ask which branch they mean.” Write it exactly as you would say it to a member of staff, and your receptionist follows it word for word.
Each rule is separate, and each can be switched off without deleting it. You choose when it applies — every conversation, or only bookings, cancellations, refunds, orders or prices — so a booking rule is never in the way on a refund call. You can mark a rule as something the assistant must never do, and set which rule wins when two of them pull in different directions.
Anything involving money can be set to hand over to you. Mark a rule “hand this to a person” and your receptionist will state it and pass the matter to your team rather than acting on it itself.
A cancelled appointment recorded nothing about why it was cancelled. So when a customer rang to ask, the honest answer was “it is marked cancelled, but I do not have a reason recorded” — the least useful thing your receptionist can say to somebody who rang up to find out.
Cancelling from the dashboard now takes a reason and an optional note, and records whether it was you or the customer who ended it. Your receptionist can then answer the question properly next time somebody asks.
If you charge for late cancellations, your receptionist says so and hands it to you. Add the terms as an instruction on the new AI Instructions page and mark it “hand this to a person”. The caller is told the charge applies before they ring off — rather than finding out when it reaches their card — and your receptionist never takes the payment, waives it, or promises either way. That is your decision to make.
When somebody already in your customer list rings from the number you hold for them, they are now greeted by their first name. “Hi, you are through to Baker Plumbing” becomes “Hi Sarah, you are through to Baker Plumbing”. It is the difference between ringing a company and ringing a company that knows you.
Only the number the phone network provides is used. A number somebody reads out over the phone is not used for this — that is the number printed on the outside of a parcel, and it is not proof of who is holding the phone. Being greeted by name also unlocks nothing on its own: what your receptionist is willing to discuss about an account is decided by the same identity checks as before, and those are unchanged.
Only a first name, and only one we are confident about. Never a surname, never an account detail, and nothing at all if the name we hold does not look like a name — imported lists often carry “Unknown” or a blank in that column, and saying that aloud is worse than saying nothing. Anyone we do not recognise, or anyone withholding their number, hears exactly what they heard before.
You can turn it off. If greeting people by name is not right for your line of work, it is a single setting in Call Studio.
Signing in now happens on a dedicated SIMCOAI sign-in service at auth.simcoai.co.uk, styled to match the rest of the product so it does not feel like being handed somewhere else. It is the same account — there is nothing new to register. Your password is now held and checked only by that service: every stored password record has been removed from your workspace, so SIMCOAI holds none at all, in any form. Password resets, sign-in links and emailed verification codes all run there too, which means your password is only ever typed into the one place built to handle it. If you sign in with Google, nothing changes and there is no separate SIMCOAI password. The old dashboard sign-in address still works and simply takes you to the new one.
There is a new reviews page on the SIMCOAI website. Every review on it was written by a real customer and published with their permission — and if there are none yet, the page says so plainly rather than showing testimonials nobody wrote.
About two weeks after you start, we will email you once to ask whether you would like to write one. Fourteen days rather than a few, because by then your receptionist has answered real calls and you are describing the product rather than the setup. It is one email; there is no follow-up, and the unsubscribe link in it stops feedback requests without changing anything about your billing, security or service emails.
Three things we have committed to in writing, because a review page is only worth reading if you know how the reviews got there. We do not offer discounts, credit, free months or anything else in exchange for a review or for a particular rating. We do not filter by star rating — critical reviews are published alongside the rest. And a review is marked as coming from a verified customer only when it arrives through the single-use link in that email, which is something our systems decide and nobody can ask for.
Every review is read by a person before it appears, and you can have yours taken down at any time by emailing us, without giving a reason. The full commitments are in the Terms, and what happens to the personal data in a review is set out in the Privacy Policy.
Call Studio has always let you test your receptionist before pointing your phone line at it. Until today you did that by typing, which skips the part of a real call most likely to go wrong: whether it actually hears you. You can now press a button, speak, and have it answer — using the same speech recognition that runs on your live phone line.
It shows you what it heard. A misheard word is the commonest fault on any phone call and the caller never finds out; here it is written on screen next to your own turn, so if your service names or your business name are being misheard you can see it and fix it before a customer rings.
The panel now behaves like a call rather than a chat box. It tells you whether it is connecting, speaking, listening or thinking, counts the call length, and lets you replay any answer. You can still type instead — the receptionist answers the same way either way.
What it does is written in plain English now too. When a call logs a booking it says so; when it still needs a detail before it can, it says that. It used to show an internal status label and repeat the sentence the receptionist had just said, which looked like a fault.
One honest note: the spoken replies in this browser test are currently played back with your own browser’s voice rather than the SIMCOAI voice, while we sort out capacity with our speech supplier. Your real callers are unaffected — phone calls use a separate route and still use the SIMCOAI voice throughout. The panel says which one you are hearing rather than leaving you to guess.
SIMCOAI has kept a record for each of your customers for a while now — it is how the AI recognises a regular from the number they are ringing from instead of asking them to spell out an email address again. Until today that list sat under Growth in your dashboard, which is not where anyone looked for it, and the only way to put a customer on it by hand was to wait for one to ring.
The customer list is now its own page under Operations, next to the orders, refunds, bookings and escalations that are attached to it. That is where you were looking, and it is where it belongs.
You can also bring in the list you already hold. Download a template, or use an export from whatever you use now, and import it. We read the usual column names — and the variations, so “Email Address”, “Mobile”, “Surname” and “Organisation” all land in the right place — and a column named after one of your own custom fields is read into it. Anyone already on your list is matched on their email address or phone number and updated rather than added a second time, so re-importing the same file changes nothing and a nightly export is safe to run again and again.
You are told what happened to every row: added, updated, already on file, or skipped and why. A row with neither an email address nor a phone number is named rather than quietly dropped, because there would be nothing for the AI to recognise that person by. And you can export your list back out as a spreadsheet whenever you want it, on any plan.
Editing a customer is better too. It used to be three small browser boxes asking for a name, then an email, then a phone number, one after the other, with no way to see what you were changing and nothing else editable at all. Now it is a proper form on the page, with their company, notes, status and your own custom fields on it.
If you connect SIMCOAI to your own website or systems, you could already send us orders, refunds, bookings and escalations — but not the customer those records belong to. The one thing everything else hangs off was the only thing you could not read or write from outside the dashboard.
You can now list, look up, create and update customer records through the API, and send someone straight from your checkout or booking form into SIMCOAI. Creating a customer is a safe repeat: we match on the email address or the significant digits of the phone number, so replaying your customer list does not create a second copy of somebody already on file, and a blank field you send never wipes a detail we already hold.
Customer records use their own permission, separate from orders and refunds. An integration that only needs to file refunds is not handed your whole contact list with them, and you choose which it gets when you create the key.
Your systems can also be told when something changes rather than having to keep asking. Alongside the existing refund, booking, order and escalation notifications, we now send one when a customer record is created or updated.
Our privacy policy, GDPR page, terms and cookie policy all listed three AI model providers we might use. In practice your account has only ever run on one of them, and one of the three was never switched on at all — it had no credentials and could not have answered a single message.
We have removed the other two from the product and from every policy page, so the list of companies that can process your data is now exactly the list that does. Fewer suppliers with access to your customers’ conversations, and a policy you can check against reality rather than take on trust.
Nothing changes for how your AI answers: every account was already running on the provider we have kept. The model choices in your dashboard — Economy, Fast, Balanced and Premium — work exactly as before.
If we ever add a provider back, it goes on the policy pages before it processes anything, not after.
In August we removed five capabilities from the plan comparison because they were not finished, and said so at the time. We have now found that two of them were still being sold elsewhere on the same page: a panel describing who Pro suits listed “advanced analytics”, and the Enterprise wording offered “multi-location” features. Neither exists as a product today.
Both are gone, along with the same two claims in the files we publish for AI assistants to read. That second part matters as much as the page itself: when someone asks an assistant what SIMCOAI includes, it answers from those files, so a wrong line there gets repeated to people who never visited our site.
What Pro actually gives you over Growth is more call minutes, more phone numbers, full API access, department routing, proof-upload links and unlimited team accounts. Enterprise is a custom agreement for high call volume, larger number capacity and bespoke terms. The plan comparison table itself was correct throughout and has not changed.
The check that keeps unfinished features off the comparison table only ever looked at the table, which is exactly how these two survived in the wording around it. It now reads the whole pricing page and both assistant files as well, so a claim cannot come back in prose without failing a build.
A handful of sections in the dashboard are still being built — the phone app, multiple locations, plugins and a few others. Opening one of them showed our own engineering notes instead of an explanation: internal headings, a list of web addresses from inside our system, and a block of raw technical output. It read as though the feature was there and had gone wrong, when the truth is simply that it is not finished yet.
Each of those sections now says that we are still building it, what it will do when it arrives, and which parts of SIMCOAI you can use in the meantime. They are included in your plan and you are not being charged separately for them. If one of them is something you want sooner, there is a link to tell us — it genuinely affects what we build next.
What is includedLogging an order, refund, booking or escalation used to mean typing the customer’s name, email and phone number again every time, even for someone you deal with weekly. Worse, a single typo in the email created a second record for the same person, and their history then sat split between the two with nobody able to see the whole of it.
All four forms now start with a search box over your customer list. Type a name, an email or a phone number, pick the person, and the record is attached to them. If they are not on your list yet, add their details there and they are added to it when you save. Every customer also has their own page now, showing their details, your own custom fields, and everything they have ever ordered, booked, been refunded, escalated, called about or sent you as proof — in one place instead of six.
Customer databaseWhen the AI recognised a caller it would talk about their account straight away. Recognising somebody and having checked who they are is not the same thing, and the difference matters most on the calls where it is easiest to get wrong: a phone number read out over the phone proves nothing, because it is the one detail printed on the outside of the parcel.
Someone ringing from a number already on their record is recognised automatically, as before — the phone network tells us the number before they say a word, so there is nothing for them to do and nothing changes for them. Anyone else is greeted by name if we think we know them, and asked to confirm their name and the email address on the account before anything on it is discussed. Until they do, the AI can still take a new booking, order or refund from them — it simply will not read the account back. A caller who gives their own email address or an order number is still helped with the records that match it, exactly as before.
Every check is recorded, so a customer’s page shows whether their identity has ever been confirmed and how. Nothing is required from you and no setting has changed.
How callers are identifiedUntil now every booking, refund and order carried its own separate copy of the customer’s details, and nothing joined them up. A person you had dealt with twenty times was a stranger on the twenty‑first, and the AI had to ask for an email address on every single call — the least reliable thing that happens on a phone line. There is now one record per customer, matched on their email address or phone number, and the AI recognises whoever is calling from the number they are ringing from and uses what you already hold. Records are created for you as calls come in, and everything that customer has ever booked, ordered or asked for a refund on sits on one page. You can add your own fields too — a flat number, a boiler model, a policy reference — and the AI can read those on a call.
Customer databaseOur plan comparison listed customer records, a mobile companion, plugins, multiple locations and advanced analytics as included features. Going through the page line by line, those five were not finished products — the groundwork exists, but there is nothing a customer could open and use. They should not have been on a page people buy from, so they have been taken off it entirely rather than reworded or marked “coming soon”.
Nothing you are paying for has been taken away, and no plan price has changed. If any of these mattered to your decision to sign up, please tell us — we would rather hear it. They will go back on the page when they are real.
See the comparisonOur billing policy now sets out how prepaid credit works: it is drawn down by usage, it stops at zero rather than building a bill you have not seen, and automatic top-up stays off until you turn it on and is capped by a monthly ceiling you choose. Our telecoms policy has also been corrected — the AI and recording notice at the start of a call is set by us and applied to every call, so it is no longer described as wording you are responsible for choosing. Your own greeting is still yours.
Read the billing policyThe pricing page used to hide each plan’s features behind a dropdown, which made the one thing you go there to do — compare — the hardest thing to do. There is now a full comparison of every feature and all twelve usage allowances side by side, generated from the same limits the platform enforces on your account.
Compare plansSet your bookable hours, how long each service takes and how many you can run at once, and the AI offers times from that diary instead of taking a message. It will not offer a slot that is already full, one you are closed for, or one that has already passed — and it understands how people actually say times, from “half past two” to “the first one”.
How the timetable worksWhen someone rings about a booking they made three weeks ago, the AI can now find their record from the number they are calling on and answer from it, rather than telling a regular customer it has nothing on file. It only ever discusses the caller’s own records.
What the AI can seeSigning in to SIMCOAI now happens on a dedicated, hardened login page instead of a form inside the dashboard, so your password is never typed into a SIMCOAI screen. Passkeys, authenticator apps, email sign‑in codes, and Google or Microsoft accounts are available where enabled for your account, and signing out ends the login session too. Your business data stays where it always has, on SIMCOAI‑controlled infrastructure.
How sign-in worksTrial reminders, invoices, receipts, payment notices, product updates and workflow alerts now arrive as clearly branded SIMCOAI emails.
Read updateMarketing, news and basket recovery emails are opt-in by default. Billing, security and workflow messages remain operational and logged.
Privacy policyUntil you set a timetable, a caller asking for an appointment gets their details taken and passed to your team. Once you have added your bookable hours, the AI offers actual times from your diary and confirms them on the call.
When a caller asks for a time that has gone, the AI says whether it is already booked or you are closed then, and offers alternatives — rather than sounding like it could not find anything.
Three things a caller notices straight away once a timetable is set.
Bookings are available on Growth and Pro plans.
From trial reminders to invoices and workflow alerts, every message from [email protected] uses the same clean SIMCOAI design, with your preferences and unsubscribe choices respected on every send.
The SIMCOAI logo is now inside the email body. The small Gmail sender avatar is controlled by mailbox/domain branding, not the HTML template alone.
These domain records help receiving mailboxes trust SIMCOAI messages and are required groundwork for advanced logo display.
BIMI requires a domain policy and a hosted SVG logo, and many receivers require a verified certificate for full logo display.
Google BIMI guidanceSome inboxes also show the sender account profile image. That must be configured in the sending mailbox/provider account.
