Included with every new account

A public website,
not just an app.

A branded site under your own address, the Terms and Privacy pages a real messaging campaign needs, and a form that turns a visitor into an attributed lead in your inbox.

Watch it come together

One site, five things it's already doing.

The brand goes on first. Then the site itself. Then the page starts showing up in a search result. The legal pages publish alongside it. And the form at the bottom reaches your inbox with the visitor already attributed to how they found you.

Not a landing page

A complete site, published under its own address.

The public site a visitor reaches at your subdomain (or a custom domain we point at it) is rendered from the same content your team edits in the console - hero, services, values, testimonials, and the request form - so it stays in sync with your brand without a separate build. Adding a page or a section is a content edit, not a deployment.

Found, not just live

A page that describes itself to search and social.

Each company's site is rendered server-side with its own page title, meta description, and Open Graph preview image - your branding if you've set one, your logo if you haven't - so a link shared to a group chat or dropped into a search result shows your business, not a generic placeholder.

We don't promise a ranking. Nobody controls that, and a page that says otherwise is not describing this product.

The paperwork a campaign needs

Terms, Privacy and the SMS disclosure - published, not drafted by you.

Every company's site publishes its own Terms of Service and Privacy Policy at /terms and /privacy, generated from an attorney-drafted template written to the CTIA / 10DLC disclosure format: the exact opt-in language, the STOP/HELP handling, and the no-sharing clause a carrier looks for when it reviews an A2P 10DLC campaign.

Publishing the page is the foundation a campaign registration needs - it is not the same as a carrier approving that campaign, which is a separate review. See how Valletto handles the rest of A2P 10DLC registration.

Somebody found you

A lead in your inbox, not a name in a spreadsheet.

The request form on your site captures the visitor's details together with how they arrived - UTM parameters, referrer, and the page they landed on - and stores it against your company. The submission is rate-limited and checked against a hidden honeypot field before it ever reaches your inbox, and it is emailed to your listed contact address the moment it lands.

What this is: capture, attribution and a notification. It is not a CRM or a pipeline board, and we don't track what happens after the lead reaches you.

What's still ahead

Three things we won't claim yet.

A custom domain is real, but it's configured by our team today, not a self-service setting. A page with better metadata is not a guaranteed search ranking - nothing in this product decides that. And publishing your Terms and Privacy pages is the paperwork a 10DLC campaign needs, not an automatic carrier approval.

The same operation, five sides