A2P 10DLC and Toll-Free Verification Setup for FieldCamp SMS

Register your business, brand, and campaign through FieldCamp's compliance pages so US carriers reliably deliver your SMS.

If you send text messages to customers in the United States from FieldCamp, you need to complete A2P 10DLC registration (for local 10-digit numbers) or toll-free verification (for 8XX numbers) before US carriers will reliably deliver your SMS. FieldCamp routes messaging through Twilio, and the compliance flow is built into the Calls integration in FieldCamp's settings.

A2P (Application-to-Person) 10DLC is the US carrier framework for sending business messages from local 10-digit long codes. Toll-free verification is the parallel process for 8XX numbers. Without either, US carriers (AT&T, T-Mobile, Verizon) heavily throttle or block unverified traffic — meaning your customers may never get the text.

Why US SMS compliance matters for field service

Field service businesses rely on SMS for confirmations, ETAs, "tech is on the way" pings, payment reminders, and review requests. US carriers require every business sender to register a brand (your company) and a campaign (the type of messages you send) before high-throughput delivery is granted. Without registration:

Messages may silently drop or get marked as spam.
Per-message carrier fees can increase (unregistered 10DLC traffic incurs a surcharge).
Sending numbers can be suspended after a carrier complaint.

Verifying your number protects deliverability and is a one-time setup. If you haven't yet set up calling and messaging inside FieldCamp, start with the calls setup and usage guide.

Choose your number type: 10DLC vs toll-free

Pick the number type that matches how your team communicates. You can run both — many businesses use 10DLC for local customer texts and a toll-free number for broader campaigns.

A2P 10DLC (local number)

Best for two-way customer conversations from a local area code. Requires a Trust Hub business profile, a registered brand, and a campaign tied to your sending number.

Toll-free verification (8XX)

Best for businesses already using a toll-free line for calls. Requires a single verification form covering business info, use case, and opt-in evidence.

Before you start: gather your business details

Carriers and Twilio's vetting partner cross-check the information you submit against business registries. Have these ready before you begin — incomplete or mismatched submissions are the most common cause of rejection.

Legal business name exactly as it appears on tax documents.
EIN (Employer Identification Number) for US-registered companies, or business registration number for sole proprietors.
Business email, website, and address.
Authorized representative — first name, last name, email, phone, and title.
Industry (the FieldCamp Trust Hub form lists: Automotive, Education, Financial Services, Food & Beverage, Healthcare, Home Services, Insurance, Legal, Manufacturing, Marketing, Non-profit, Real Estate, Retail, Technology, Transportation, Other — most field service businesses select Home Services).
Sample messages for each use case (appointment reminders, dispatch updates, invoice notifications) written the way your customers will receive them.
Opt-in evidence — a live URL or screenshot showing where customers consent to SMS (your booking page, intake form, or signed work authorization).

Match the business name and address to your company profile in FieldCamp so customers see consistent branding across estimates, invoices, and texts.

Register your A2P 10DLC brand and campaign

FieldCamp's compliance flow is a three-stage process: create a Trust Hub business profile, register a brand under that profile, and then launch a campaign describing the messages you'll send.

Open the compliance page in FieldCamp

Go to Settings → Apps & Integrations → Calls, then navigate to the compliance area at /settingsV2/addons/calls/compliance. The compliance page shows three steps: Business Verification, Number Registration, and Campaign Setup.

Create your Trust Hub business profile

On the compliance page, click Start Verification under "Business Verification Required" to open the business information form. Enter your legal business name, EIN, business email, industry, website, business address, and authorized representative details, then submit. FieldCamp's message states: "Review typically takes 1-2 business days."

Register a brand

Once your Trust Hub profile is approved, open the A2P 10DLC section from the compliance page and click Manage Registration. Create a brand by choosing an industry vertical and a brand type. The brand type options are Standard, Low Volume, and Sole Proprietor — the in-app helper text reads "Most businesses should select Standard."

Pick a use case and create a campaign

Add a campaign under your brand. The use-case dropdown includes Customer Care, Account Notifications, Marketing, Mixed/Marketing, Delivery Updates, 2FA, Fraud Alert, Higher Education, Polling & Voting, Public Service Announcement, and Security Alert. Most field service teams pick Customer Care or Mixed/Marketing. Fill in a campaign name, description, and at least one sample message that mirrors a real template you plan to send.

Confirm opt-in and keyword fields

The campaign form pre-fills these defaults, which you can edit:

Opt-in keywords: START, SUBSCRIBE
Opt-out keywords: STOP, UNSUBSCRIBE
Help keywords: HELP, INFO
Help message: "Reply HELP for help"
Opt-in message: "You have opted in to receive messages from us."
Opt-out message: "You have been unsubscribed from our messages."

These values are sent to Twilio as part of the campaign metadata.

Attach your sending number to the campaign

After the campaign is approved, return to the A2P 10DLC tab and associate one of your active local phone numbers with the campaign. The compliance page filters local numbers automatically — toll-free numbers go through a separate verification flow.

Wait for review

Brand vetting timelines are set by Twilio and carriers, not FieldCamp. The brand-creation success toast says: "Brand registration submitted successfully! Verification typically takes 1-3 business days." Campaign approval timelines are governed by Twilio and the carriers and are not set by FieldCamp.

Submit a toll-free verification request

Toll-free verification (TFV) is a single form rather than a brand + campaign flow. It lives inside the same compliance area of FieldCamp.

Make sure your toll-free number is active in FieldCamp

The number must already be provisioned in FieldCamp before you can submit verification. The toll-free page filters your phone numbers to show only the toll-free prefixes (800, 833, 844, 855, 866, 877, 888).

Open the toll-free verification form

From the compliance page, open the Toll-Free Verification section and click Manage Verifications. The form has three parts: business info (pre-filled from your Trust Hub profile if it exists), use case info, and opt-in info.

Fill in use case and message details

Pick a use-case category, write a summary, paste at least one sample message, and estimate monthly message volume. The volume options in the form are: Less than 1,000/month, 1,000–10,000/month, 10,000–100,000/month, 100,000–1M/month, More than 1M/month.

Describe how customers opt in

The opt-in type dropdown lists: Website Form, Mobile App, SMS Keyword, IVR/Phone, Paper Form, Other. You can also attach opt-in screenshot URLs. Carriers reject TFV submissions that don't show clear SMS consent language, so name SMS specifically — generic "we may contact you" copy is not enough.

Submit and wait for review

FieldCamp's success toast reads: "Toll-free verification submitted successfully! Review typically takes 7-10 business days." During review, traffic from the number sends at unverified throughput.

Do not start broadcasting high-volume marketing texts before approval. Sending high volumes from an unverified toll-free number can trigger carrier-level blocks that take days to lift.

Document a clear opt-in flow

Carriers reject submissions when they can't see how customers consented to receive texts. Your opt-in evidence should match how FieldCamp actually collects customer info — through online booking, request forms, manual intake, or signed estimates.

Online booking customers opt in via the booking widget. Review your setup in the online booking guide and make sure SMS consent language is visible before the submit button.
Phone-in customers opt in verbally — note this in your campaign description and keep an intake script or check-the-box prompt.
Existing customers can be migrated if you stored consent at signup. Your CRM record is the place to track opt-in source and date.
Estimate and quote signers can opt in via a checkbox on signed estimates.

A strong opt-in line includes three things: your business name, the type of messages they'll receive ("appointment reminders, dispatch updates, and billing notifications"), and a STOP-to-opt-out plus message/data rates disclosure.

After approval: test and maintain

Once your brand and campaign (or toll-free form) are approved, send a test text to your own phone and to a teammate, then confirm:

Messages arrive without "Likely Spam" labels.
The sender number matches what you registered.
Your business name and templates render the way you expect inside FieldCamp's client communication records.

Keep your registration healthy by:

Reviewing message templates quarterly so they still match what carriers approved.
Updating sample messages if you launch new automations (for example, recurring service contracts).
Refreshing brand info when you change legal entity name, address, or EIN.
Tracking deliverability in your two-way text messaging inbox — sudden delivery drops can be a compliance signal, not a technical bug.

Add automated SMS steps in your workflow builder only after verification is approved. That way every reminder and follow-up benefits from full carrier throughput from day one.

Troubleshooting and FAQs

Why is my brand registration stuck in "Pending Vetting"? Standard brands go through a third-party vetting partner managed by Twilio. The most common cause of long pending times is an EIN-to-name mismatch — open your brand record and confirm the legal name is character-for-character identical to your IRS filing.

My campaign was rejected for "insufficient opt-in evidence." What now? Carriers want a live URL or a clear screenshot showing the exact consent checkbox and SMS language. Update your booking page to include a dedicated SMS consent line ("I agree to receive appointment and dispatch text messages from [Business Name]. Reply STOP to opt out. Msg & data rates may apply."), then resubmit.

Can I keep using my existing Twilio number? Yes — local numbers already in FieldCamp can be attached to an approved brand and campaign from the A2P 10DLC tab. No port-out or new purchase is needed.

Do international numbers need 10DLC? No. 10DLC is a US-only framework. Canadian carriers have their own (currently lighter-touch) rules, and other regions have separate sender ID processes.

Are there messages I can't send even after registration? Yes — the "SHAFT" categories (Sex, Hate, Alcohol, Firearms, Tobacco), cannabis, and high-risk financial offers remain restricted by carriers regardless of brand status. Field service messaging almost never trips these.