Source Tokens
Source tokens determine which profile your automated messages appear to come from on Yelp and Thumbtack. When you connect for example John’s profile, all bot responses appear from “John”.
Key Point: Each source token represents a specific person’s profile. The bot always responds using that person’s name and identity.
What Source Tokens Do
- Identity: Determine whose name appears on all automated responses
- Access: Grant permission to manage specific business locations under that profile
- OAuth: Provide secure API access to platform messaging systems
Adding Source Tokens
- Navigate to Source Tokens page and click the ”+” button
- Login to Yelp/Thumbtack with the profile you want the bot to represent
- Authorize NZ Leads to access business locations under that profile
- Verify the imported locations match your expectations
Critical: You must be logged into the correct profile during OAuth. That person’s name will appear on all future automated messages.
Transferring Sources to Different Tokens
Sometimes you need to change which profile represents a location (employee departures, consolidation, etc.).
Enable Transfer
- Go to Sources page → click Edit on the source you want to transfer
- Enable “Allow transfer to another Source-Token” toggle
- Save the source settings
Execute Transfer
- Add or refresh the source token for the profile you want to receive the source
- The system automatically transfers the source during token refresh
- Verify the source now appears under the correct token
- Transfer flag automatically disables after completion
Transfer Timing: The actual transfer happens when you add/refresh a token that contains the transferable source.
Common Issues
Missing Locations
- Verify the connected profile has admin access to those locations
- Use “Update List” button to refresh available locations
Transfer Not Working
- Ensure transfer flag was enabled before refreshing the token
- Check billing is active for the receiving business
OAuth Problems
- Make sure you’re logged into the correct profile during connection
- Clear browser cache if authentication fails
Best Practices
- Only connect profiles of current team members
- Monitor token expiration dates and refresh before they expire
- Use dedicated business profiles rather than personal accounts when possible
- Document which profiles manage which locations for team reference
Understanding source tokens is essential for managing your bot’s professional identity. Proper setup ensures customers see consistent, appropriate contact names on all automated communications.
For assistance with source token setup, contact support@nzleads.com