Texting is hands down the most effective way to make sure your message gets seen. If you're unsure about using texts to engage with agents and leads, ask yourself this - how many unread emails do you have right now compared to unread texts?
Due to recent telecom carrier standards, you must register for verified calling and texting detailed here to enable texting in your account.
From the Recruiting or Retention screen, please select a contact to open their profile. Along the top action bar, click Text. 
The first time you send a text with Brokerkit, you'll need to choose a number the system will use for all your outgoing texts. Add your local area code and choose an available number. Then, enter the number you'd like all calls and replies forwarded to. Click here to learn why you need a system number to text with Brokerkit.
When a contact replies to a text, the reply will show up in your inbox, it will automatically be forwarded to your forwarding number (typically your mobile phone) and logged in Brokerkit under the contact's Recent Activity.
We have a character counter that will be displayed when your text message exceeds one segment. To learn more about text message billing, review the help article here.
Below is an example of how a multi-segment SMS text message will appear in Brokerkit.

Since you can also send MMS messages with images, the segment counter will also show the number of segments that your MMS message contains:
Outbound texts include compliance text — your Profile Friendly Name as a footer, plus a "Reply STOP to unsubscribe" line — depending on the conversation. As of May 2026, the compliance text is conversation-aware.
⚠️ The rules below apply to every outbound text — one-on-one texts sent from a contact's profile, bulk texts, and campaign texts. There is no difference in how compliance text is applied across these message types. Each recipient is evaluated individually based on their conversation history with you on this Brokerkit number.
For any outbound text, the conversation state determines what compliance text (if any) is appended:
| Recipient's conversation state on this Brokerkit number | Profile Friendly Name footer | "Reply STOP to unsubscribe" line | Result |
|---|---|---|---|
| Contact texted you first (contact-initiated conversation) | No | No | Clean message |
| Contact has previously replied in this conversation | No | No | Clean message |
| Cold — first message ever to this conversation | Yes | Yes | Full compliance |
| Cold — opt-out was sent in this conversation in the last 30 days | Yes | No | Footer only |
| Cold — opt-out was last sent in this conversation 30+ days ago | Yes | Yes (re-inserted) | Full compliance |
A "conversation" is a specific contact + Brokerkit number combination. The same contact on a different Brokerkit number is a separate conversation with its own independent compliance state.
What "full compliance" looks like:
{your message}
{Profile_Friendly_Name}
Reply STOP to unsubscribe
Examples in practice:
- A one-on-one text to a brand-new lead → footer + "Reply STOP" (full compliance).
- A one-on-one follow-up to that same lead the next day → footer only (within 30 days).
- A one-on-one follow-up after they reply → clean.
- A bulk text to a list of 100 leads → most cold recipients get the footer + "Reply STOP" treatment, while recipients who've already engaged with you on this Brokerkit number get clean messages.
- A campaign step that goes out to a contact who replied to a previous step → clean.
The placement, the "Reply STOP" wording, and the conversation-aware skip rules are not user-configurable — they are set by Brokerkit to stay compliant with TCPA regulations.
You can customize your Profile Friendly Name:
- For Accounts within an Organization: Navigate to Account Settings and edit the "Office or Team name" field.
- For Standalone Accounts: Navigate to Phone Number settings and edit the "Profile Friendly Name" in the Business Profile tab.
The first reply text you receive from each contact will be forwarded to your forwarding number and include the candidate's contact information and a link to the contact profile in Brokerkit, so you know to whom you are speaking. If you ever lose or delete that message, reply with ?who to the text chain, and Brokerkit will send you a new text with all the contact's information.
Scheduling a text
You can schedule a text to be sent whenever it is convenient for you. Compose a text, and before sending it, click on the clock icon next to the Send Text Message button.

A pop-up will appear, so you can default settings or custom select the date, time, and time zone that better works for you.
- In 1 hour
- In 2 hours
- Tomorrow Morning (AM)
- Tomorrow Afternoon (1 PM)
- Custom (see image below)

NOTE: The options above will be sent according to the timezone in your Brokerkit user settings unless you choose a custom timezone.
*NOTE: Brokerkit uses two timezone settings that affect scheduling:
- User Settings Timezone: Your personal timezone for scheduling (click your name → User Settings)
- Account Settings Timezone: Your team/office timezone (click your name → Account Settings - Admin only)
Scheduled messages will use your User Settings timezone by default unless you choose a custom timezone. For proper synchronization, ensure both timezone settings are configured correctly.*
How to stop a scheduled text from sending?
Scheduling a text via the contact profile, you can cancel the delivery before it is sent. To do that, follow these steps:
- Open contact profile from where you want to delete the scheduled message
- In the Activity timeline under the ALL tab or TEXT tab find the scheduled text

- In the right of the event log. Click on the Trash icon

- Confirm you want to delete it
- The event log will then show that the Scheduled text was deleted

Editable Profile Friendly Name for Brokerkit Texts
What’s New
- Admin users can now edit their account’s Profile Friendly Name—the name contacts see when you text from your Brokerkit number.
- The profile friendly name must remain a recognizable version of your registered name, but you can now shorten or simplify it for a more personal touch.
- Updates to your profile friendly name are reflected instantly in all outbound texts.
- No support tickets needed—Admin users can make changes directly from the account UI.
How to Get Started
For Accounts within an Organization:
- Log in to Brokerkit as an Admin.
- Navigate to your Account Settings.
- Locate the "Office or Team name" field and edit it.
- Save your changes to update your team's friendly name.
For Standalone Accounts:
- Log in to Brokerkit as an Admin.
- Navigate to your Phone Number settings.
- From the Profile Status or Business Profile tab, edit the Profile Friendly Name.
- Save your changes.
Make your first impression count—one text at a time. Happy Texting!
Verified Texting Approval Timelines
The time to enable texting depends on your account status:
New Accounts Setting Up Verified Texting (First Time)
- Timeline: 7-14 business days
- Includes business profile review and texting use case approval
- You'll receive email updates on your approval status
Adding a New Phone Number to an Existing Approved Campaign
- Timeline: Approximately 1 hour
- Only applies if your business profile and texting use case are already approved
- Simply add the number and resubmit for carrier approval
To check your current approval status, navigate to Phone Number → Verified Texting tab.
Troubleshooting: "Phone number not linked to approved verified texting campaign"
What this means: Your phone number needs to be added to a verified texting use case before sending texts.
Quick fix:
- Click your name in the upper right corner
- Select Phone Number from the menu
- Go to the Verified Texting tab
- Add your BrokerKit phone number to the use case
- Click Submit to send for carrier approval
- Wait approximately 1 hour for the new number to be approved (Note: This assumes your business profile and texting use case are already approved. New accounts take 7-14 business days for initial approval.)
Note: Each phone number must be approved individually. Any time you add a new number, you must resubmit the use case for approval.