Al klant bij Spur?

Inloggen
Masking & shared users

Hide customer numbers from your team

People can read and reply to a conversation without ever seeing the customer’s phone number, WhatsApp username or profile name.

Number masking

Masking is a setting on the Spur user. Every frame minted for a masked user is masked:

  • The header shows a masked number, such as +91 98•••• ••97, and no name. The copy-number and click-to-call buttons are hidden; other copy buttons, on messages and notes, work as normal.
  • Events carry only the masked number, and spur:authenticated has masked: true so your page knows to hide its own copy.
  • Masking is applied to the data Spur sends to the frame, not with CSS, so it holds up against browser devtools.
  • A masked user can’t sign in to the Spur dashboard or app for that workspace. They only use Spur through your CRM.

Turn it on

  1. Invite the user to your workspace and wait for them to accept.
  2. In Settings → Team, open the user and turn on Hide contact identity.
  3. Mint tokens for that user. The setting applies at once to anything an open frame loads next; reload open frames so what’s already on screen is masked too.

Workspace owners can’t be masked, and you can’t mask yourself.

Limits

  • Message content isn’t masked. If a customer types their number or sends it as a contact card, the user sees it. Template variables aren’t masked either.
  • The mask only holds if your page hides the number too. Keep phone numbers out of your browser code entirely: frame URLs and commands take IDs for exactly this reason, and your server’s calls with the number go straight to Spur, never through the browser.

One Spur user for your whole team

You can mint every token for a single Spur user, usually with masking on. It’s supported, and it’s the quickest way to roll out to a large team. What you give up:

Attribution

Every message, note and status change in Spur is recorded as that one user. “Replied by Priya” becomes “Replied by CRM”. If you need to know who said what, log it in your CRM (spur:messageSent and spur:conversationStatusChanged tell you when).

Assignment and routing

Round-robin, team routing and “assigned to me” views have one user to work with.

Reports

Per-user reports in Spur show one row.

Collisions

Spur sees one user, so two people can open and reply to the same conversation without seeing each other.

Access is on your side

Nobody signs in as the shared user, so there’s no shared password to rotate: removing someone’s access to your CRM removes their access to the embed. Give the shared user a long random password nobody holds.

If you later want per-person attribution, routing or reports in Spur, give each person their own Spur seat and mint tokens for them. Nothing else in your integration changes.