One address. Your CRM updates itself.
Copy it onto the reply you were already sending. Add it as a guest on the meeting you were already booking. That is the entire workflow, and there is nothing to install.
Re: Twelve seats, and the May migration window
Copy the address on a reply you were sending anyway. The message lands on that customer’s timeline, attributed to whoever wrote it, and the colleague on Cc stays a colleague.
Every other CRM asks you to change how you work.
Install a plugin, memorise a personal BCC string, open a sidebar before you write, or come back afterwards and log the call. None of these is broken. They just all depend on somebody doing an extra thing, at the exact moment they are busiest, for a benefit that lands on somebody else's screen a week later. That is why CRMs go stale in good months rather than bad ones.
- Install this extension
A plugin in one browser, on one machine, for one member of the team. It does not follow anybody to their phone, and it stops the day IT tightens the extension policy.
- Remember your personal BCC
A different opaque string per user, which nobody can check for typos and nobody notices has been silently wrong for a fortnight.
- Log the call afterwards
The step that gets skipped first in the week where the most is happening, which is how a record ends up thinnest exactly where the deal got interesting.
Viably asks for none of it. Your workspace claims one address, it looks like [email protected], and it is the same string for everybody on the team however many inboxes you run.
Working out who a message is about is the hard part.
The address says which workspace. Everything after that is read off the message itself, which is what separates this from forwarding a copy into a folder somebody has to sort later.
It knows which of you is you
Members who linked an account, addresses you verified, and every domain you claimed. A colleague on the thread is never captured as a contact, so a shared record does not slowly fill up with the people you work with.
It picks the counterparty
The first recipient outside your workspace, with a To beating a Cc, because the person a message is addressed to is its subject and everyone copied is an observer. Nobody outside on the message means nothing is recorded at all.
It checks the sender is real
A message claiming to come from one of your own addresses has to pass DMARC before it is written down as your reply. A forged message on a customer record would be worse than no record.
It files where the conversation lives
A lead who arrived through your website and was answered from Gmail a week later reads as one relationship. Which of your inboxes received the copy is not a question anybody has to settle.
A record should know the call happened.
A contact enquires, somebody books a call with them, and in most CRMs those two facts never meet. The record shows a form submission going quiet at the exact moment the relationship was at its healthiest. The same address closes that, from the same gesture, on the invite you were sending anyway.
The limits are the product.
Anything that reads mail or calendars is asking for a lot of trust, and the honest way to earn it is to be narrow on purpose. Each of these is enforced in the code that writes the record, not promised in a policy document.
- It cannot read the mail you did not copy it on
There is no mailbox scanning and no read access to your email, so the capability begins and ends with the address being on the message. Nothing of yours is legible to Viably unless you put it there.
- A meeting can never create a contact
An entry is written only for attendees already in your contacts. A calendar entry full of colleagues, candidates or your own appointments is read and discarded without a trace, which is what makes reading a calendar defensible at all.
- Nobody switches your calendar on for you
Meeting logging is per member and off until that member turns it on themselves. Adding the address as a guest needs no calendar access in the first place, which is the route most teams stay on.
Two one-time steps, and the second one is optional.
Create an inbox endpoint so your workspace has somewhere for mail to land, then shorten the handle that sits inside the address. Viably picks a handle for you if you would rather skip it, though a short one is easier to say out loud and it is claimed globally, so it is worth taking the one you want early.
It works from anything that can put an address in a Cc field.
Gmail, Outlook, Apple Mail, a phone on a train, and whatever the one person on your team who refuses to switch is still using. There is no OAuth grant, no extension and no change to how anybody sends mail, because an ordinary recipient is all it ever was.
Read how the routing worksQuestions about the shared address
Use it once and the record is waiting for you.
Start free, create an inbox, and copy the address onto the next customer email you send.
- Free to start
- The free plan needs no card
- Powers on when you need them