One business phone number, everywhere

Saving the company phone also mirrors it to the organisation record, so the messaging token and the invoice can never print different numbers.

What it is

The business phone is stored on the invoice settings row and simultaneously pushed to the org record used by the messaging token and the client portal, keeping one number across documents and messages.

Also called: wrong phone number on invoice · company phone token · phone shows up different

See it
One business phone number, everywhere
Prepared for
Delia Yoder
1140 Ridge Line Rd · Fair Play
Shell package$26,331
Concrete & site$7,645
Doors & windows$5,096
Trim & finish$3,398
Total
$42,470
Signature
Not visual — show the phone field saving, and the same number appearing on an invoice header and in a message preview. Sample data — no customer information appears here.
How it works
  1. 1Saving company_phone (on blur or via Save Business Info) also posts to /api/settings/business-phone.
  2. 2That endpoint writes the org-level phone that the {{company.phone}} token and the portal read.
Why we built it

The comment names the bug class directly: 'theclass of bug: a stray default phone printing on invoices'. Two stores holding a phone number meant one of them was eventually wrong on a document a customer reads.

The problem
  • The messaging token and the invoice header read different phone stores.
Sound familiar?
What you get
Customers always get the number you actually answer.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →