Three Rivers RenovationsPNG, JPEG or WebP · maximum 256 KB. The preview keeps your logo’s original colors.
The export contains only the business name and logo. Friends need their own accounts, connections and private app setup.

Use your approved work email.
Connections, webhooks, nurture drips and your account.
Set the business name and logo for this copy of Team Hub.
Three Rivers RenovationsPNG, JPEG or WebP · maximum 256 KB. The preview keeps your logo’s original colors.
The export contains only the business name and logo. Friends need their own accounts, connections and private app setup.
Office follows before booking and stays through Sales until the project sells: this is the approved Office policy. The default keeps Office following between booking and estimate day. Sales joins on estimate day. Upon sale, automatic Office and Sales subscriptions are removed and Production joins.
The proposed handoff default keeps explicit manual and @mention follows until that person unfollows. Saved policies remain authoritative, including any review hold. Follow controls the personal Following view, not security access. Sales and Production team views and existing mention access remain unchanged. Rescheduling, cancellation, loss and reopening events require review before automatic changes.
Automatic routing requires an approved pilot customer and approved staff recipients for that customer. Saving mappings does not add anyone to that pilot scope. You can still Follow or unfollow accessible customers manually while automation is off or outside the pilot.
Estimate introductions, review links and production welcome messages need separate script and sending approval. Saving these settings sends no messages.
Connection changes are managed by an administrator. Setup snapshot: October 9, 2026. This page does not check live provider health.
Provider keys stay in protected server settings. Team Hub does not accept, reveal or save them in this page.
Business calls and texts
An administrator must approve a backend credential setup before connecting Quo. Quo API keys grant full account API access; the key must stay on the server.
Confirm number readiness and messaging registration before approving an end-to-end test.
Quo API access guide ↗Shared customer email
Approve the mailbox and requested permissions, then use a secure Google authorization flow. A Google password or API key is not entered in Team Hub.
Staff login and saved team work
The app uses a public browser key with database access rules. Administrator keys and provider secrets belong in protected backend settings.
Customer and deal context
Approve the records and events to sync, then configure API access on the server. Existing PaintScout workflows remain managed in PaintScout.
Automation delivery
Review the exact scenario, trigger and customer outreach before approving a connection. Existing scenarios are managed separately in Make.
Webhooks bring new activity from a service into Team Hub.
Before activation, approve the receiving address, number, events and data being stored. Verify signed deliveries and duplicate handling before relying on message updates.
No other provider webhooks are configured for Team Hub.
Automation controls are not connected. No campaigns or customer messages can be started here.
Use Nurture Drips to review wording. Running an automation requires a separately reviewed connection and approval.
Move the blue sidebar to the right on desktop. Your inbox and conversation stay in their usual order.
A personal display preference. When account settings are connected, it is saved to your staff account. Phone layout always stays unchanged; your desktop preference returns on a wider screen.
Review message wording by PaintScout stage and day.
No prepared message is available for this selection. Review the stage notes for intentional silence or pending copy.
Choose how you are alerted when a teammate mentions you. Email is the default; SMS is optional.
Alerts will link to the private conversation. Sign-in and existing customer access still apply. These preferences are only for your account.
Alerts require an approved pilot customer and an approved staff recipient for that customer. Preferences do not add customers or people to the pilot scope.
Staff approval controls access to Team Hub. The site's current private access gate also still applies.