What is 10DLC and does Strkr handle the registration process?
10DLC (10-Digit Long Code) is the US-mandated framework for business SMS traffic. Businesses register their brand and their specific SMS campaigns (use case, sample messages, consent flow) with carriers via The Campaign Registry (TCR). Approved brands and campaigns get substantially higher throughput and reduced carrier filtering. Unregistered or lightly-vetted SMS gets heavily filtered. Strkr handles the registration workflow through the admin console: brand registration, campaign submission with use-case description and sample messages, consent flow documentation, carrier-side vetting. The process typically takes 7 to 14 business days for approval. We provide registration templates for the common use cases (sales outreach, appointment reminders, two-factor codes, account alerts, surveys) and guide the admin through the brand-verification steps. The one-time registration fee and monthly campaign fee pass through transparently in the Strkr Messaging line.
How does Strkr handle TCPA class-action risk?
TCPA class-action risk is one of the biggest exposures in business SMS. The posture: structured consent capture per contact with source, timestamp, and chain of custody; immediate opt-out honoring across the workspace on STOP keyword variants; calling-window enforcement to prevent after-hours sends; audit log of every send, consent, opt-out, and override that is immutable for class-action defense; DNC registry respect; 10DLC campaign vetting that establishes legitimate business use. The combined posture is substantially stronger than the ad-hoc patterns most CRMs use, and the audit log is specifically designed to produce the artifacts a TCPA class-action defense needs. For teams with specific compliance review requirements, we provide the full compliance documentation and audit sample for procurement and legal review.
Can Strkr send MMS with images, documents, and video?
Yes. MMS support covers images (JPG, PNG, GIF up to roughly 1 MB per carrier limits), documents (PDF up to roughly 5 MB), and short video clips (MP4 up to roughly 1 MB). The exact size limits vary by carrier; Strkr returns transparent error messages when a send exceeds a carrier's limit. Common use cases include receipt-photos (service motion), property-images (real estate), appointment-intake forms (healthcare), and promotional-visual campaigns. The MMS per-message cost is higher than SMS (typically 2x to 3x) and the pricing is disclosed openly in the Strkr Messaging documentation.
How does the pricing work for high-volume SMS?
Strkr Messaging pricing has three components disclosed openly. Base: a flat workspace subscription that covers up to a specified monthly message volume. Per-message markup: a small markup above the carrier's per-message cost (disclosed in the pricing documentation). Carrier-fee passthrough: the per-message carrier fee that US carriers assess for 10DLC traffic (varies by carrier and campaign tier, passed through at cost). For teams running very high volume (over 100,000 messages per month sustained), bundled plans are available. The combined cost on a mid-market team sending 20,000 to 50,000 messages per month typically runs 30 to 50 percent lower than the equivalent Twilio-plus-HubSpot stack because the integration overhead and per-user license drops to zero. We publish the full pricing model openly for comparison math.
How does inbound SMS routing work when a prospect replies?
Inbound SMS routes by priority rules: first, caller ID matched to an account owner (the rep assigned to the account receives the reply); second, skills-based routing (match inbound-intent keywords to specialized teams); third, round-robin fallback within the appropriate team. The routing is admin-configurable and composes with team-hour schedules so after-hours inbound routes to the on-call team or an auto-responder. The reply threads to the original conversation on the contact record so the rep sees the full exchange chronologically. For teams running a shared SMS inbox pattern (any available rep can pick up the next inbound), the admin configures the pool and the rotation.
Can we send transactional SMS like two-factor codes alongside marketing SMS?
Yes with campaign separation. Transactional SMS (two-factor codes, account alerts, order confirmations, appointment reminders) and marketing SMS (promotional offers, newsletter content) register as separate 10DLC campaigns with different throughput tiers and different consent requirements. Transactional campaigns typically approve faster because the use case is clearly transactional; marketing campaigns face stricter vetting. The admin configures which rep groups or Flows can send to which campaigns. The pattern avoids the common mistake of running transactional and marketing on the same campaign, which both constrains transactional throughput and raises carrier-filtering risk on the marketing side.
How does Strkr compliance posture work for HIPAA-regulated SMS and international markets?
Strkr is HIPAA compliant with a Business Associate Agreement available for teams sending SMS containing protected health information (appointment reminders, lab-result notifications, prescription refills in healthcare SaaS). The posture includes encrypted message storage, role-based access to conversation history, audit logging, and configurable retention per record type. For international SMS (UK, EU, Canada, Australia, Latin America), carrier-level routing uses the local in-country sender when available and respects the local regulatory frameworks (PECR in the UK, GDPR consent requirements in the EU, CASL in Canada, APP in Australia). Opt-in capture tracks the jurisdiction so cross-border sends respect the local rules automatically. For high-regulation markets (specific EU member states with stricter rules, Switzerland, Singapore), the admin can configure per-market rules. The combined posture satisfies the common regulated-industry procurement review and has passed audits with several healthcare and financial-services customers running international motion.
