← Back to Blog
product-update embedded-signup onboarding

Onboarding in English, Spanish, and Portuguese

Ler em português →

Short version: the public Embedded Signup page now speaks English, Spanish, and Brazilian Portuguese. You can lock the language when you create the link. If your customer reopens that same link later to finish a pending step, the page stays in the language you chose.

The problem

A lot of PipesBot customers onboard numbers for teams in Latin America. The product they already use is in Portuguese or Spanish. The public page at /apps/$slug was English-only, so the first thing those people saw — before Meta’s dialog, before a PIN, before the number was ready — was a page in the wrong language. Integrators also had no way to pick the language themselves.

How the language is chosen

The page picks a language in this order:

  1. The locale you pass when you create the signup token, if you pass one. The accepted values are en, es, and pt-BR.
  2. The customer’s browser languages, in order. Regional variants match on the language: pt-PT shows Brazilian Portuguese, es-419 shows Spanish.
  3. English, if nothing else fits.

Pass locale when you already know the customer’s language — for example, from their account in your product:

{
  "redirectUrl": "https://yourapp.com/onboarding/complete",
  "locale": "pt-BR"
}

That goes on POST /v1/apps/token, the same call you already use to create the link. Any other value returns 400 with locale must be one of: en, es, pt-BR.

The locale is stored in the token you put on the signup URL. When onboarding continues, it is copied onto the registration ticket, so a customer who reloads the page or comes back days later to finish a pending step still sees the language you forced.

If you don’t pass locale, the page follows the browser — including older tickets created before this change, which stay valid.

Error messages on the public page follow the same language. The server keeps a stable error code next to the English error string; the page translates by that code, so the customer isn’t asked to “try again” on a link that has already expired.

What this does not change

A few things on the path are outside this setting, and it’s better to know that up front:

  • Meta’s signup popup uses the language of the customer’s Facebook account. The PipesBot page and the popup can disagree.
  • Your App’s name, logo, and tagline stay exactly as you wrote them.
  • The PipesBot dashboard stays in English. Numbers you connect from the dashboard are not affected.

Try it

Create a token with locale set to en, es, or pt-BR, and send your customer to the usual signup URL:

https://app.pipes.bot/apps/{your-app-slug}?token={token}

The Embedded Signup docs cover the locale field and the rest of the token API. If you want the full picture of what happens after the customer finishes the Meta dialog — registration, PIN, Coexistence — read Cloud API numbers now register themselves after Embedded Signup.