Your email
Search and read mail with each person's own read-only access, so it can never show one person another's inbox. Gmail first, then Microsoft 365. Parked until the first read-only answer works.
For Gold Coast and South East Queensland businesses
The private assistant in your team chat that knows your email and back end
Arke Bot is an internal assistant for your staff. It lives in your team group chat, answers from your business email and back-end software, and only talks to verified staff. It is not a customer-facing chatbot.
Join the waitlist See what it connects to
Early access. Build in progress. Anything not live yet is marked Coming
#ops team chat
Staff only
Scene 1 of 2
Scene 1: an order question
Priya, sales@Arke where is order 1042, and has the customer emailed us about it?
Checked: Priya is verified staff in this chat.
Read only, answered in this chat
Order 1042 was packed yesterday and is waiting for courier pickup. There is one email thread from the customer asking for a delivery update. Nobody has replied yet.
Sources: order system, shared inbox (example data)
Priya, salesCan you draft a reply for me?
Proposed draft, waiting for approval
Approved by Sam, sent
Here is a draft: "Hi, thanks for your patience. Your order is packed and with the courier, and we will send tracking once it is collected." Nothing is sent until you approve it.
Proposed email draft, not sent
ApproveEditReject
Approved, logged in the audit log
Scene 2: stock and an email thread
Tom, warehouse@Arke how many Canvas Tote Bags are on hand, and what did the supplier say in the latest thread?
Checked: Tom is verified staff. Read only access.
Read only, answered in this chat
The stock system shows 12 Canvas Tote Bags on hand. The supplier wrote on Tuesday that the next delivery is delayed by a week and asked you to confirm the order.
Sources: stock system, supplier email thread (example data)
Tom, warehouseWhat is the supplier asking me to approve? Also, what is the bank account on that invoice?
Read only, answered in this chat
The supplier asks you to confirm the revised delivery date. I can only show masked payment details in a group, so I have not included the account number. I can send the full details to you by direct message if you are allowed to see them.
Redacted in group chat, logged
Staff only. Nothing leaves this chat.
Illustration only. Fictional staff, orders and data. Planned product, marked Coming.
Staff onlyverified staff in your team chat, nobody else
Read firstit looks things up before it is ever allowed to act
You approveno email or change goes out without a verified approval
You can stop ita kill switch and an audit log you control
See it in action
Arke Bot and Magic Pay together: chat, book and pay in one place.
Salon booking
Book a cut and blow-dry and pay the deposit in chat.
Online store
Pick a product, check out and track delivery in chat.
Mobile service
Quote, book, remind and take the final payment in chat.
Clinic ordering for Aliquot
Order, track shipping and pay the monthly invoice in chat.
Connected to your email and back-end software
Ask in plain words in your team chat. Arke Bot looks it up, answers with where the answer came from, and waits for approval before any action. Each card shows where that part of the build stands.
Your back-end systems
Orders, stock, bookings and other business records, through fixed read-only lookups you agree: tables, columns and row limits. No free-form database access.
Your private knowledge
Procedures, tone and escalation rules kept in a separate private store, never mixed with anything public. Answers must cite their source.
Approval-gated actions
Draft an email or update a record as a proposal. A separate function re-checks identity, role and content before it runs, and the AI never holds that credential. Read only first.
Trainable, safely
Your own AI helpers can propose knowledge, tone and guardrail changes through a training API. They are tested in a sandbox, and no API key can publish.
Owner dashboard
Staff approvals, spaces (pause and resume), connectors, training drafts, the private audit log and the kill switch, scoped by role.
Later, actions such as sending an email or updating a record are proposals first. A verified approver sees exactly what will happen and approves it. Coming
In your staff-only team group chats
It answers only verified staff, and in groups only when someone mentions it. WhatsApp is the lead channel we plan to start with, then Slack, Google Chat, Microsoft Teams and a staff-only Messenger. Every channel is Coming and nothing is switched on yet. Pick one to see where it stands.
WhatsApp (lead channel)
Planned first: chat one to one with the assistant, with each staff phone number checked against your staff list on every message. Staff groups are only possible on Official Business Account numbers where the Groups API is confirmed, with a maximum of 8 people, so we are not promising them. Not built yet.
Slack
Planned for invite-only channels. It replies only when mentioned, and each person is checked against your staff list on every question. Not built yet.
Google Chat
Planned, for Google Workspace businesses. Not built yet.
Microsoft Teams
Planned, for Microsoft 365 businesses, in group chats and team channels. Not built yet.
Private Messenger
Planned as a one-to-one staff-only chat on a dedicated Page. Only staff you have verified are answered. Not built yet, and subject to Meta's rules.
Arke Bot works only in invite-only groups that you create, where it is a member with permissions you set for that group. Coming
Arke Bot is for your staff only. Public customer channels such as SMS, Instagram and customer-facing Messenger or WhatsApp are not part of this product.
Slack, Google Chat, Microsoft Teams and Messenger are parked until the first read-only answer works.
How it works
Every question goes through the same checks, in code and outside the AI.
Ask
A staff member mentions @Arke in an owner-enabled, invite-only space or one-to-one chat.
Verify
Their chat account is matched to an active staff record and role, checked on every message. Guests get nothing.
Look up
Allow-listed, read-only tools only. Email and records are treated as untrusted data, never instructions.
Filter
Redaction before the AI and again before posting. The output filter strips links and leaks.
Answer
A reply with sources in the thread, or by direct message when the data is restricted.
Audit
Who asked, which sources and tools were used, and the decision go into an insert-only log.
Writes
Any action, such as sending an email or changing a record, becomes a proposal. It needs a second verified person to approve it and runs through a separate function with a credential the AI never sees. A single-owner business stays read only.
Built for a team's private information
Being in the chat is not permission. These protections are the plan, and each one is Coming unless noted.
Verified staff only Coming
- Only verified staff can use your private team chat.
- Every person is approved by you and checked on every message.
- If someone unknown joins, Arke Bot checks the member list and pauses answering, and alerts you. Not every chat platform reports new members, so this depends on the platform.
- Each person only sees the data their role allows.
- Every check is recorded in an audit log you can export.
Invite-only groups with special bot permissions Coming
Arke Bot only works in invite-only groups that you create. It is a member of the group, and you set what it is allowed to do in each group. In any other chat it stays silent.
Verified staff
Each person links their chat account to a staff record once. Guests, outside users and people who have left get nothing, and the check happens on every question.
Audit log
Every question, source used, answer, refusal and approval is recorded in a log you can view and export. Nobody can edit it.
Approval before actions
It starts read only. Any later action waits for a verified approver, and the assistant never holds the credentials that do the action.
Kill switch
Stop the private assistant at any time, for the whole business, one chat or one person.
Sensitive details protected
Card numbers, tax file numbers and similar details are masked in group chats, and restricted answers go by direct message.
Separate tenant per business
Every business is its own tenant with no shared data, with row-level security on every table. The database is in Sydney.
Two people to approve a write
Writes need a second verified approver. A single-owner business runs read only.
Sandbox and go-live checklist
Every change is tested in a sandbox with zero sends. Go-live is blocked until every check passes.
Treats emails as untrusted
Text inside an email or document is data, not instructions, so a malicious message cannot make it send or share anything.
Built so far: staff identity and the membership guard, the audit log, redaction, the kill switch, the training API with sandbox and owner approval, and the output filter. Connectors and chat channels are still to come.
Easy setup
Arke runs the setup with you. Nothing goes live until every check passes.
Create the business
Arke sets up your own tenant, owner login, hours, industry and a regulated flag.
Staff and roles
Owner, manager, staff and viewer. You approve each linked chat identity.
Spaces and data
Invite-only spaces switched on, and your back end connected through a read-only view.
Training draft
Knowledge, tone, escalation and guardrails as one draft. API keys cannot publish.
Sandbox checklist
A full pre-go-live checklist in a sandbox that never posts. Go-live is blocked until all checks pass.
Approve and go live
You review the changes and results, approve, and watch the switch-on.
Checked before and after go-live
9 general checks for every business, including sourced answers, permission boundaries, write dry runs, tone, escalation, injection and the kill switch. After go-live, corrections become new drafts, you can roll back by re-approving an older draft, and the kill switch is on every screen.
Trainable by your own AI helpers
Built A training API lets the owner's own AI helpers propose knowledge, tone and guardrail changes and test them in a sandbox that never posts to your chat. Nothing goes live until the owner approves it. No API key can approve or publish.
Who it is for
Any team that works from a shared chat and keeps its information in email and business software: trades, property managers, clinics and practices, tourism and accommodation, gyms, retail and professional services.
No industry is excluded.
Health and regulated onboarding. Health and regulated businesses are welcome, with training, setup and guardrails. For these teams the private assistant starts switched off and is turned on only with the owner's written sign-off, after 3 extra clinical checks. Answers with sensitive details go by direct message, and patient records are not connected. Arke Bot does not diagnose or give medical advice.
Progress and roadmap
The engine is running. The pilot path comes next.
- Private database, roles and row-level security
- Staff identity and membership guard, audit log, redaction, kill switch
- Training API, sandbox and owner approval
- Output filter
- Owner dashboard: staff, spaces, connectors, training, audit
- Read-only back-end connector and business loader
- Daily AI spend cap, owner go-live screen, per-business tone
- Isolation proof, and writes locked until a second approver exists
- WhatsApp one-to-one staff channel live, then Slack, Google Chat, Teams and private Messenger
- Per-person Gmail connector, then Microsoft 365
- Approval-gated write actions
Pricing
Pricing to confirm. There is no final price yet for the private assistant. Pilot pricing on request.
We expect pricing to be based on the private assistant for your team, with onboarding as an option. Details to decide.
FAQ
Is this a customer-facing chatbot?
No. Arke Bot is a private assistant for your own staff, in staff-only team chats.
Who can ask it questions?
Only verified staff. Being added to a chat is not enough, and guests and outside users get nothing.
Can it send emails or change records?
It starts read only. Later actions are proposals that a verified approver must approve first. Coming.
Which chat tools will it work in?
Planned: WhatsApp first, then Slack, Google Chat, Microsoft Teams and a staff-only Messenger. All are coming, and none is switched on yet.
Can it see everyone's email?
The plan is for each person to connect their own read-only access, so it shows only what that person could already see. Coming.
What if I need to stop it?
A kill switch pauses the assistant for the business, a chat or a person. Every question and approval is also in an audit log.
Can my own AI helpers train it?
Yes. The training API is built. It lets your own AI helpers draft and test changes, and only you can approve what goes live.
Can I use it for a health or regulated business?
Yes, with no industry exclusions, using our onboarding with training, setup and guardrails. It is off by default for these teams, patient records are not connected and sensitive answers go by direct message.
Where is my data kept?
The database is hosted in Sydney. The AI service is provided overseas, which our privacy policy will state once it is finalised.
Is it available today?
Not yet. This is early access, and anything not built is marked Coming.
What does it cost?
Pricing to confirm. Pilot pricing on request.
Join the waitlist
Tell us about your business and we will be in touch about early access.