For larger teams
If the account has your company’s name on it, start with a conversation.
Vexo is self-serve and most teams should just sign up. This page is for the ones where somebody has to answer for what gets published: several brands, several regions, or a legal team who will read the agreement before anyone opens the product.
Tell us roughly how many brands and which networks. You will get a reply from a person within one working day, not a scheduling link.
What the engagement is
A person, not a queue
One named contact at TouchBase who knows your account. Same person in the setup call and the one six weeks later when a post goes out wrong.
Setup done with you
Connecting the accounts, writing the brand description Vexo works from, and reading the first run of drafts together before any of them publish.
A shared channel
Slack or email, whichever you use. Not a ticket form.
Terms that get reviewed
A DPA and an agreement your legal team can mark up, rather than a checkbox on a signup page.
What we would tell you on the call anyway
- No SSO against your identity provider, and no automated deprovisioning.
- No SOC 2 or ISO 27001. There is a full account of what we do and do not hold on the security page.
- One region, keys managed by us. No data residency choice.
- Workspaces are separate, but there is no single console across all of them yet.
If any of those is a hard requirement, say so in the first email and we will tell you whether it is months away or not on the list. The full account is on the security page.