They prepare. You decide. They learn from what you decided.

Gmail, Outlook, Google and Microsoft calendars, LinkedIn, Meta, Google Ads and Stripe. You are shown what each will be able to do before you agree, permission to send or change anything is asked for separately from permission to read, and the tokens are encrypted at rest.

Forward mail to the private address your workspace is given. It arrives, is deduplicated, is marked with how far it should be trusted, and is kept against your workspace.

Publish an address that reaches one specialist and give it to a supplier, a client or your accountant, the way you would give somebody an extension to dial. Front it with an address on your own domain if you have one — annette@yourcompany.com, forwarded in — and to the person writing, Annette works for you. Say in your own words what arrives there and what you want done with it, and whether each one is dealt with as it lands or taken together on a round. What they send is read as information and never as an instruction, whoever the message claims to be from; the answer comes back to you rather than to them; and each address has a ceiling on what it can take in a day.

What is being sold, where each one has got to, and — the part a board on its own never tells you — what has had nothing happen to it in a fortnight and what is owed this week. Your Sales Rep moves deals, writes down why, and keeps the next step current. Every stage change is kept, so how long things sit in each stage is a question with an answer rather than a feeling. There is no weighted forecast: that number is made up in every product that offers one, and people plan against it.

A Lead Researcher reads company sites, department pages and public registers for people who fit, writes down the page each one was found on, and says which are worth your time and which are not. It never invents an email address — a guessed one bounces, and the bounces are charged against your own domain, so your invoices start landing in spam weeks later. Connect a Hunter or Apollo account you already pay for and it uses that too: your key, your credits, your agreement with them. If you already keep contacts in Apollo, bring them straight into your own contact book — anything you already hold is filled in where it is blank and never overwritten, and every disagreement is recorded so you can see what the other tool said.

A few messages, spaced out, each written to the person rather than merged from a template — and the whole thing stops the moment they reply. It goes out from your own domain or the mailbox you connected, never from us. It refuses anybody whose address was guessed rather than published, refuses anybody nobody has qualified, and holds a daily ceiling you set.

Reading a mailbox, filing it, replying, holding time in a calendar, posting, texting, operating an ad account.

A number of your own that your staff answer. They know who is ringing before anybody speaks — a customer who called last week about a leak is greeted as that customer, not as a stranger — and they can send a booking link while the caller is still on the line, offering only times that are genuinely free. Recorded calls come back as a summary in Messages. Robocalls are ended before they eat your minutes. United States and Canada only for now. A separate add-on, priced separately.

Working, and United States and Canada only. Choose an area code, see what numbers are genuinely free, pick one, and it is bought, bound to your staff and answering within about twenty seconds — nobody at Operenda touches it. Elsewhere the phone network wants proof-of-address paperwork for each number, which cannot be done while you wait, so we would rather say so than take the money and explain afterwards.

A chat box on your own site, answered by the same staff who answer your phone and your mail — so it knows your prices, your hours and what you already told the last person who asked. It only runs on the addresses you allow, there is a limit on how much one visitor can send, and every conversation appears in Messages so nothing lives only in a widget.

A thread you can add to your phone's home screen. Ask for something the way you would ask a colleague, send a photograph or a document, and decide what is waiting on you without opening anything else. Your staff answer in the same place, and the phone reports its calls there too.

Attach a picture and whoever picks the message up can see it. Documents are kept and shown to you, and a specialist is told plainly that it cannot open one rather than discussing a contract it never read.

Speak into the thread and hear the answer, hands free, without ringing anything.

Not built. It needs a speech-to-text vendor this deployment has no account with, and a price per minute for turning speech into text and back — until both exist we would be guessing at the cost of a feature people would use for hours. Your staff answer the phone today, and that lane is metered and honest about what it charges.

Add Operenda to an iPhone properly, so your staff can reach you without the site having to be on your home screen first. Everything inside it is the same as the website, so nothing works differently depending on where you opened it.

The app is built and runs, and the part of it that receives notifications is written and has never delivered one — that needs an Apple push key this deployment does not have, and a place in the App Store. On Android, a Mac and a PC notifications already work from an ordinary browser with nothing to install.

Connect your phone once and message your staff from WhatsApp. They answer there, and the whole exchange also appears in Messages. Your number is proved by sending a code from the handset, because a number typed into a form proves nothing.

Attach a picture or a document to a WhatsApp message and your staff can see it.

Not built, and refused plainly rather than silently dropped — send it from the app instead, where it works. Fetching what somebody attached needs a second authenticated call to Meta and somewhere to put it, and a photograph that vanishes is worse than one that was turned down.

The same thread, from Telegram.

Not built. It needs a bot token and a webhook and nobody's approval, and the seam it would use is the one WhatsApp already goes through.

Mail going out as your business, refused unless SPF and DKIM are verified so your domain is never used unauthenticated.

Send through the Gmail, Outlook, iCloud or Fastmail account you have already connected, with no domain and no DNS — and replies land in that account's own Sent folder.

It is built and it is not proven. Nothing has yet gone out of a real Gmail, Outlook or iCloud account through it — what has been checked is the message we build, the way each provider is asked, and every refusal. If you have no domain of your own, this is the route that lets your staff finish a job instead of stopping at the draft, and we would rather you were the first with us watching than find out from a customer who never got the email.