What does "built-in SMS" mean versus an integrated messaging platform?
Built-in SMS means the messaging capability lives natively inside the CRM: the conversation threads on the contact record, the compliance (A2P 10DLC, consent, DND) runs on the CRM audit log, the sending numbers assign through the CRM admin, and the per-message cost sits on the same invoice as the CRM license. An integrated messaging platform is a separate product with its own account, its own compliance surface, its own audit trail, connected to the CRM via API webhooks that your team maintains. Built-in collapses the stack to one tool, one bill, one audit log. Integrated keeps the specialist depth but requires ongoing engineering and ops time to keep the two systems in sync.
How does Strkr handle A2P 10DLC registration?
Strkr handles brand registration and campaign vetting through its established carrier relationship. The team provides the brand information (legal entity, EIN, use case description, sample message templates) and Strkr submits the registration. Typical go-live time is 3 to 5 business days versus 10 to 20 business days on a developer-platform self-serve path, because the carrier relationship is pre-established and the campaign shapes are familiar to the review process. The brand trust score and campaign throughput match the industry baseline for the team's traffic class. Enterprise verification is available for brands running above the standard throughput tier.
How are DND, consent, and opt-outs handled?
Every outbound send checks DND status on the contact and the account before firing. Inbound STOP, UNSUBSCRIBE, QUIT, END, CANCEL (and localized equivalents) auto-mark the contact as opted-out and block future sends until the contact re-opts in explicitly. Consent capture stores on the record (where the contact opted in, when, by what channel, with what disclosed) for the compliance audit trail. The audit log retains for 7 years, which exceeds the TCPA 4-year statute of limitations. For campaign types that require it (health, financial, political), the national DND registry imports on request. The operational outcome is that the compliance officer's quarterly review runs as a filtered report in a single audit log, not a cross-system reconciliation.
What does built-in SMS actually cost compared to a developer-platform integration?
Strkr's messaging adds a $29 monthly base per tenant plus transparent per-message cost (currently $0.02 per SMS, $0.05 per MMS) to the flat per-seat CRM line. For a 40-rep team sending roughly 4,000 messages a month, the all-in SMS cost runs about $109 per month on top of the CRM. A typical horizontal-CRM-plus-developer-messaging-platform stack at the same volume runs $800 to $2,000 per month combined: $500 to $1,500 messaging base, per-number fees, compliance registration fees, per-message spend, plus integration maintenance time. The three-year delta on a 40-rep team routinely runs $25,000 to $70,000 in direct cost, before counting the integration engineering time the native capability recovers.
Can Strkr send MMS with photos, videos, or PDFs?
Yes. MMS supports image attachments up to 5 MB per message, short video clips, and PDF attachments. The sales rep sends a product photo from the mobile tablet surface; the agency sends a creative mockup from the desktop; the recruiter sends a job description PDF; the HVAC technician sends a photo of the equipment issue. Attachments store on the thread history and in the sent-messages archive for compliance retention. Pricing is $0.05 per MMS regardless of attachment type below the standard size limits. For home services, mortgage, insurance, and real estate motions where photos and PDFs are routine parts of the workflow, MMS is the capability that unlocks the pattern.
What happens when a prospect replies to a Strkr SMS?
The inbound reply surfaces on the contact record in real time with a notification to the owning rep within seconds. The thread updates with the reply visible in context. If the reply triggers a sequence branch (for example, a positive reply to a demo-booking SMS), the sequence advances to the appropriate next step automatically. If the reply is an opt-out keyword (STOP, UNSUBSCRIBE, etc.), the contact auto-marks as opted-out and future sends block. For teams running shared numbers (support, concierge), the reply surfaces to the shared inbox with assignment, status, and @mention. Reply latency from carrier delivery to visible on-record is typically under 5 seconds, which is dramatically faster than webhook-driven integration patterns where the latency often runs 30 to 60 seconds.
