Skip to main content
Phone Number controls how your whole organization sends SMS and handles calls. You choose one of two setups: an in-platform number that ProPilot provisions for you in seconds, or a connection to your own Quo (formerly OpenPhone) workspace. Every teammate sends and receives from the same organization number.
Key things to know
  • Your organization uses one active phone setup at a time: the in-platform number or a connected Quo number, never both.
  • Without a number, SMS sending fails with an error asking you to provision or connect one, so set this up before any outreach.
  • Only org owners and admins can provision a number or connect Quo.
  • With the in-platform number, incoming calls can ring directly in your browser once you click Enable incoming calls.

​
Where to find it

Open Settings from the sidebar, then choose Phone Number under Basic Setup.

​
Choose your setup

Pick the in-platform number if you want the simplest ProPilot-native setup. Pick Quo if your team already lives in a Quo workspace and wants ProPilot activity tied to that number. For the full Quo walkthrough, see Quo Integration.

​
Set up the in-platform number

1

Choose an area code (optional)

Under Get an instant number from us, enter a 3-digit US area code, for example 415. Leave it blank to let ProPilot pick one.
2

Click Configure number

ProPilot provisions the number for your organization. All members will send SMS from it.
3

Enable incoming calls

On the connected panel, check the Incoming calls status. If it shows Disabled, click Enable incoming calls so inbound calls to your number ring in ProPilot in the browser. Use Refresh to re-check the status at any time.

​
Connect a Quo number instead

1

Generate an API key in Quo

In your Quo workspace, generate an API key and copy it.
2

Paste the key in ProPilot

On the Phone Number page, open the Quo panel and paste the key. ProPilot validates it automatically.
3

Pick a number

Choose which number from your Quo workspace the organization should use. See Quo Integration for details on what syncs.

​
What this affects

  • SMS sending - Messages, Bulk Messaging, and Sequences all send from the active organization number.
  • Calls - with the in-platform number, calls ring in the browser. With Quo connected, calls open in Quo and completed call activity can sync back into ProPilot.
  • Attachments over SMS - Quo-connected organizations send and receive media through Quo.
  • The whole team - the number is organization-wide. There are no per-user sending numbers.
For day-to-day calling and texting workflows, see Phone Number in the features section.

​
Limitations

  • One active setup per organization. Connecting Quo replaces the in-platform flow; disconnecting Quo returns you to it.
  • In-platform numbers are US numbers only, and the area code field accepts exactly 3 digits.
  • Only owners and admins can provision a number. Members see a notice asking them to contact an admin.
  • Outbound texting is also subject to your plan limits and the platform’s operating hours and compliance rules. See Operating Hours.

​
Common questions

Yes. Without an organization phone number, SMS sending shows an error asking you to provision or connect a number. Set this up before launching outreach or sequences.
Yes, by connecting Quo and selecting a number from your Quo workspace. ProPilot does not port numbers directly. See Quo Integration.
No. The organization uses one active phone setup at a time. Connecting Quo makes it the active provider; disconnecting returns the organization to the in-platform number flow.
On the in-platform setup, check the Incoming calls status on this page. If it shows Disabled or “Enabled (different domain)”, click Enable incoming calls (or Fix incoming calls) and then Refresh to confirm it shows Enabled.
Calls open in Quo instead of the browser dialer, and completed call activity can sync back into ProPilot so your conversation history stays complete.
No. The organization shares one sending number, which keeps conversations with each agent in a single thread regardless of who on your team replies.