Strata Automation Hub· OS

24/7 Digital Workforce

Capture, Qualify, Deliver

Strata://Hub-OS·Gauteng, ZA

Operator Access

Briefing 01 · System

How It Works

Strata puts an AI receptionist on the channels your customers already use. It answers from a knowledge base you control, captures the enquiry, books the appointment, and hands you the lead before the visitor has closed the tab.

01

Capture

A visitor opens the web widget, messages your WhatsApp number, or calls the voice receptionist. All three run the same brain: your knowledge base, your capture schema, your calendar. The bot answers the question first and asks for details second, because a form that opens before a question is answered is a form nobody fills in.

02

Qualify

Every conversation is scored against the fields that matter to your sector. Real appointments are booked into real free slots — availability is pulled live from your Google Calendar, so the system can never double-book you. Anything the bot cannot handle is escalated to a human rather than guessed at.

03

Deliver

The lead lands in your portal the moment it is captured, and in your inbox and on your phone alongside it — email with a calendar invite attached, SMS for the alerts that cannot wait. Nothing is queued for a nightly digest.

Two runtimes, one boundary

Strata is deliberately split in half. The conversational runtime handles the public, untrusted traffic — chat widgets, webhooks, phone calls — and holds no database credentials at all. It reaches your data only through a narrow, authenticated bridge. The runtime that does hold your data never talks to the public internet; it talks to signed-in users and to that one known peer.

The practical consequence: a compromise of the noisy half does not reach the valuable half. That is the entire reason for the split, and it is why every write the bot makes is a network hop with a durable retry queue behind it.

What you see

  • The lead ledger — every enquiry, its transcript, its status, its source channel.
  • Call records — one row per voice call, enriched after the call is analysed.
  • Bookings — what was scheduled, by whom, and whether it held.
  • Lifecycle reports — Day-14, Day-30 and 90-day reviews, generated automatically.

Briefing 02 · Stack

What You Get

One deployment, three channels, and the same brain behind all of them. What follows is what a live Strata deployment actually runs — not a roadmap.

Channels

Web widget
Embedded on your site. Answers, captures and books without the visitor leaving the page.
WhatsApp
Inbound on your business number, with the same knowledge base and the same capture schema.
Voice receptionist
A real phone number that answers, qualifies and books. Every call is logged and transcribed.

In every deployment

  • Your knowledge base — you own the answers; the bot does not invent them.
  • Two-way calendar sync — free/busy pulled in, confirmed bookings pushed back out.
  • Owner alerts — email with an .ics invite, plus SMS on new leads, new bookings and handoffs.
  • Human escalation — the bot hands over rather than guessing when it is out of its depth.
  • Live-fire certification — a deployment does not go live until it has been proven against real scenarios.
  • Durable retry — if an email, a booking or a calendar write fails, it is queued and retried, not lost.

Tenancy and isolation

Every client is a tenant. Your leads, bots, transcripts and bookings are scoped to your account at the application layer and enforced again at the database layer, so a query that forgets the scope returns nothing rather than someone else's data. Defence in depth, not a single check.

Operating region

Built and operated for South African business hours — day boundaries, booking windows and lifecycle reporting all run on Africa/Johannesburg time, and billing is in Rand.

Legal · POPIA

Privacy Policy

Last updated 19 August 2026 · Governed by the Protection of Personal Information Act 4 of 2013 (POPIA), Republic of South Africa.

Strata Automation ("Strata", "we") operates the Strata Hub and the AI receptionists deployed for our clients. This policy explains what personal information we process, why, for how long, and what you can ask us to do about it.

1. Who is responsible

For information about our own clients — account holders who sign in to this Hub — Strata is the responsible party. For information about a client's customers captured by a deployed receptionist, the client is the responsible party and Strata is an operator processing on their documented instructions.

Information Officer: Mohammed Luay Saib, luaysaib786@gmail.com. Write here with any question or request about personal information, including the requests in section 7.

2. What we collect

Account information
Name, business name, email address, hashed password, tier and billing status. Passwords are stored only as a bcrypt hash — we cannot read yours.
Conversation content
Messages exchanged with a receptionist, call transcripts and call metadata (time, duration, outcome), and any details a visitor volunteers: name, contact number, email, and the enquiry itself.
Booking information
Appointment times and the calendar events created for them, where a client has connected a calendar.
Technical information
Session cookies required to keep you signed in, a CSRF token, and server logs. We do not run advertising or cross-site tracking on this Hub.

3. Why we process it

  • To provide the service you or our client has contracted for — answering, capturing, qualifying, booking and delivering enquiries.
  • To authenticate you and keep the account secure.
  • To bill for the service and to compute the reporting our clients rely on.
  • To meet legal obligations, including records we are required to keep.

4. Who else touches it

We use a small, fixed set of operators. Each receives only what its function requires:

Language model provider
Generates the receptionist's replies. Receives conversation text.
Voice platform
Runs the phone channel. Receives call audio and produces transcripts.
Messaging and SMS carriers
Deliver WhatsApp messages and alert SMS. Receive message content and phone numbers.
Payment processor
Handles subscriptions and activation fees. Receives billing details; card data never reaches Strata's systems.
Calendar and email providers
Create booking events and deliver notifications, where a client has connected them.

Some of these operators process information outside South Africa. Where they do, the transfer is made on the basis permitted by section 72 of POPIA. We do not sell personal information, and we do not share it for anyone else's marketing.

5. How long we keep it

Resolved leads are anonymised in place after 14 days by an automatic daily purge: the identifying fields are redacted and the analytical record survives without them. Account and billing records are kept for as long as the account is active and thereafter for the period South African tax and company law requires. Server logs are short-lived.

6. How it is protected

  • Transport is encrypted end to end; session cookies are HTTP-only and same-site.
  • Tenant data is isolated at the application layer and enforced again by row-level security in the database, so a scoping mistake returns nothing rather than another tenant's data.
  • Third-party credentials, including calendar refresh tokens, are encrypted at rest.
  • The public-facing conversational runtime holds no database credentials at all.

No system is perfectly secure. If a breach affects your personal information we will notify you and the Information Regulator as section 22 of POPIA requires.

7. Your rights

You may ask us to confirm what we hold about you, to correct it, to delete it, or to stop processing it, and you may object to processing. Write to the Information Officer above; we will respond as soon as reasonably possible, and within the period POPIA allows. If a receptionist deployed by one of our clients captured your details, we will route your request to that client, who is the responsible party for it.

You may also complain directly to the Information Regulator (South Africa) at inforegulator.org.za.

8. Changes

We will post any material change to this policy here and update the date at the top. Continued use of the Hub after a change means you accept the revised policy.

Legal · Agreement

Terms & Conditions

Last updated 19 August 2026 · Between Strata Automation and the account holder named on the service agreement. Your signed agreement governs where it differs from this summary.

These terms govern your use of the Strata Hub and of any AI receptionist we deploy for you. Signing in means you accept them.

1. The service

Strata provides a multi-tenant AI receptionist that answers enquiries on the channels included in your tier, captures leads, books appointments and delivers them to your portal. What your tier includes — the channels, the volume and the price — is set out in your onboarding schedule, which forms part of this agreement.

2. Your account

You are responsible for the credentials issued to you and for everything done under them. Tell us immediately if you believe an account has been compromised. One account belongs to one business; do not share access outside it.

3. Fees and billing

  • Charges are a once-off activation fee plus a monthly retainer at your tier, quoted and billed in South African Rand.
  • Billing is handled by our payment processor. The retainer recurs monthly until cancelled.
  • Usage beyond your tier's included volume is trued up on your next invoice.
  • Activation fees are not refundable once a deployment has been certified and gone live.
  • We may revise pricing on the written notice period set out in your service agreement, effective from your next billing cycle.

4. Your content, your data

Your knowledge base, your branding and the leads your deployment captures remain yours. You grant Strata only the licence needed to host and process them in order to run the service. We do not use your content to train models for other clients. You can export your lead data at any time while your account is active.

You warrant that you have the right to use the material you give us, and that you have a lawful basis for processing the personal information your deployment captures. Where Strata processes that information we do so as an operator under POPIA — see the Privacy Policy.

5. Acceptable use

You may not use the service to send unsolicited bulk messages, to impersonate anyone, to handle information you are not entitled to hold, to attempt to reach another tenant's data, to probe or overload the platform, or for anything unlawful. Deployments must not be presented in a way that misleads a person into believing they are speaking to a human when they ask.

6. Availability

We aim for continuous availability but do not warrant uninterrupted service. Planned maintenance will be notified in advance where practical. Parts of the service depend on third parties — a language model provider, a voice platform, carriers, a calendar provider — and an outage at one of those may interrupt the corresponding channel. Any service-level commitment applies only if it is stated in your schedule.

7. Limits of what the bot decides

An AI receptionist is an assistant, not an adviser. Strata is not liable for a commercial decision you take on the strength of an automated answer, and you remain responsible for the accuracy of the knowledge base it answers from. The system escalates to a human when it cannot cope; you are responsible for staffing that escalation.

8. Liability

Nothing here excludes liability that cannot lawfully be excluded, including under the Consumer Protection Act where it applies. Subject to that, neither party is liable for indirect or consequential loss, or for loss of profit or goodwill, and Strata's total liability in any twelve-month period is limited to the fees you paid in that period.

9. Suspension and termination

Either party may terminate on the written notice period set out in your service agreement. We may suspend a deployment immediately for non-payment, or for use that would expose the platform or another tenant to risk. On termination we will make your lead data available for export for the period stated in that agreement, after which it is deleted on our normal schedule.

10. Changes to these terms

We may amend these terms on notice posted here. If an amendment materially disadvantages you, you may terminate without penalty before it takes effect.

11. Governing law

This agreement is governed by the laws of the Republic of South Africa, and the parties submit to the jurisdiction of its courts.

Resource · Questions

FAQ

The questions clients ask most often, answered against what the system actually does rather than what a brochure would like it to.

Can the bot answer things I have not told it?

No, and that is deliberate. It answers from the knowledge base you control. When a question falls outside it the bot says so and escalates to a human rather than guessing — an invented answer costs you more than an unanswered one.

What happens when it cannot cope?

It hands over. Escalation is a first-class outcome, not a failure state: the conversation is flagged, you are alerted, and the transcript is waiting in your portal with the point of handover marked.

Will it double-book me?

It cannot. Availability is pulled live from your connected calendar before a slot is ever offered, and the confirmed booking is pushed back to it. If the calendar is unreachable the bot offers to take details rather than inventing a time.

How fast does a lead reach me?

As it happens. The lead is written the moment it is captured and the alerts go out with it — email with a calendar invite attached, SMS for the ones that cannot wait. Nothing is held for a nightly digest.

Can I change the knowledge base myself?

Yes. It is yours, you edit it in the portal, and changes take effect on the next conversation. You do not need us to publish a change.

What if a channel goes down?

The channels are independent — a WhatsApp outage does not take the web widget or the phone line with it. Writes that fail are queued and retried rather than dropped, so a provider having a bad hour does not cost you the lead.

Do I own the leads?

Yes. Your knowledge base, your branding and every lead captured remain yours, and you can export them at any time while the account is active. See the Terms.

Resource · Releases

What's New

What has shipped, newest first. Every line is a change that is live — nothing here is a roadmap.

August 2026 · The Hub

  • A new front door. One screen, the Strata mark, and one way in. The briefings you are reading now open over the page rather than navigating away.
  • Faster first paint. The old landing page loaded a 2.4 MB hero video; it loads none.

31 July 2026 · Quarterly reviews

  • Strategic reviews are now tracked rather than remembered — your portal shows what your tier is owed and when it is next due.
  • Automated follow-ups (Apex): appointment reminders sent to the customer, with quiet hours, a per-day cap and "Reply STOP" honoured.
  • CRM push: a signed webhook fires on every captured lead, so your CRM gets it without anyone re-typing it.

30 July 2026 · Reliability

  • Timeouts and circuit breakers wired onto calendar, OAuth and SMS — a slow upstream now fails fast instead of hanging a conversation.
  • Error reporting live across both services; static assets cached in the browser.
  • Zero known vulnerabilities in either service's dependencies.

Earlier

  • Voice receptionist — a real phone number that answers, qualifies and books. Every call logged and transcribed.
  • Two-way Google Calendar sync — free/busy pulled in, confirmed bookings pushed back out, refresh tokens encrypted at rest.
  • Twilio SMS owner alerts on new leads, new bookings and handoffs.
  • POPIA retention purge — resolved leads anonymised in place after 14 days, automatically, every night.
  • Durable recovery queue — every side-effect that fails is queued and retried rather than lost.

Resource · Help

Support

A real person reads every one of these. Write to support@strataautomation.tech.

What to send

The more of this you can include, the faster it is fixed:

  • Your company name, so we can find the right deployment.
  • The channel — web widget, WhatsApp or the phone line.
  • Roughly when it happened, and the customer's number or email if you have it. That is usually enough to pull the exact conversation.
  • What you expected, and what happened instead.

Never send us a password. We do not need one and we cannot read yours — they are stored only as a one-way hash.

Before you write

  • Bot answered something wrong? Check the knowledge base first — it answers from what is in there, and correcting the source fixes it on the next conversation.
  • Booking did not appear? Check the calendar connection in your portal; a revoked Google permission stops the sync silently at their end.
  • Lead missing? Look at the Lead Ledger before the inbox. If it is in the portal but not your email, it is a mail problem, not a capture problem.
  • Cannot sign in? Use "Forgot?" on the sign-in page. Access is provisioned by your operator, so we can restore it but the reset has to reach your inbox.

Something urgent

If a deployment is down or a channel has stopped answering, say URGENT in the subject line and include the company name. Response times and support hours are set out in your onboarding schedule.

If you think an account is compromised

Write immediately and say so. We would rather suspend a deployment for an hour than leave a door open — see Staying safe for what we do at our end.

Resource · Security

Security

What we do to keep your account and your customers' details safe, and the handful of things only you can do.

What we do

  • Your password is never stored. Only a one-way hash is kept — nobody at Strata can read it, including us.
  • Your data is fenced off twice. Every query is scoped to your account in the application, and the database enforces it again independently. A mistake in one returns nothing rather than someone else's leads.
  • The public-facing half holds no database credentials. The part of the system that talks to the internet cannot reach your data directly at all.
  • Third-party keys are encrypted at rest, including the Google Calendar permission you grant us.
  • Sessions are HTTP-only and same-site, so a script on another page cannot read or reuse them, and every state-changing request carries an anti-forgery token.
  • Sign-in attempts are rate limited, and the Hub loads nothing from a third-party origin — no external fonts, scripts or trackers.
  • Resolved leads are anonymised after 14 days, automatically. We hold less of your customers' data over time, not more.

What only you can do

  • One account per person. Sharing a login means an audit trail that cannot tell you who did what.
  • Use a password you use nowhere else. Most account compromises are a password reused from a site that was breached.
  • We will never ask for your password — not by email, not on a call. Anyone who does is not us.
  • Check the address before you sign in. Your portal is only ever on this domain; a sign-in page anywhere else is not ours.
  • Remove people who leave. Tell us the moment someone with access should no longer have it.

If something looks wrong

Unexpected sign-in, a lead you do not recognise, an email that looks like us but reads oddly — tell us straight away at support@strataautomation.tech. Reporting something that turns out to be nothing costs an email; not reporting something that turns out to be real costs a great deal more.

If a breach ever affects your personal information we will notify you and the Information Regulator, as POPIA requires. See the Privacy Policy.