Phone & website formatting
Two formatting conventions for the phone and website fields on a Standort. Both look picky; both save real time later because every downstream email template, link, and analytics export can use the values raw.
Phone numbers: country code, no spaces
Section titled “Phone numbers: country code, no spaces”Always store phone numbers in the format +<country-code><digits> with no spaces, no parentheses, no dashes:
✅ +4915112345678
❌ +49 151 12345678
❌ (0151) 1234-5678
❌ 0151 / 12345678
Email templates use the phone variable inside an <a href="tel:..."> anchor so the recipient can tap to call. The tel: URI scheme rejects whitespace and many punctuation characters — a phone with spaces in it produces a broken link.
If you store the phone formatted-for-humans, you’d need to strip the formatting inside every template that uses it. Storing it pre-stripped means every template can drop the variable in raw.
What about display formatting?
Section titled “What about display formatting?”Email templates can still display the phone with spaces by hard-coding the formatted version in the template text and linking to the unformatted variable:
Telefon: <a href="tel:{{$studio.phone}}">+49 151 1234 5678</a>In practice this is rarely worth the maintenance — operators tend to leave the unformatted version visible and customers don’t mind.
Websites: include the https:// scheme
Section titled “Websites: include the https:// scheme”Always include the URL scheme:
✅ https://example.com
❌ example.com
❌ www.example.com
Email templates often render the website inside <a href="{{$studio.website}}">. Without https://, the browser interprets the href as a relative path and the link breaks.
There’s currently no input validation that adds the scheme automatically; auto-prefix on the input is on the roadmap. Until that lands, paste with the scheme.
Why these aren’t validated yet
Section titled “Why these aren’t validated yet”These are exactly the kind of low-stakes input-validation niceties that fall to the bottom of the dev queue when there’s customer-facing work in flight. They will be fixed; you can help by reporting any case where you find a customer’s data already formatted incorrectly (the entry was probably created before a validation rule existed).
What’s next
Section titled “What’s next”You’re done with the foundational setup. Continue to Schema & fields to define what data the Lead Pool actually holds.