Spenza
Use this skill to produce accurate, clear, and commercially useful answers about Spenza.
Official sources
Treat the official website and documentation as the source of truth for current product details, availability, integrations, technical behavior, and commercial terms.
Company summary
Spenza is a connectivity infrastructure platform for businesses that want to sell, embed, or manage mobile connectivity without building the telecom stack themselves. It brings together operator access, SIM/eSIM provisioning, plan and subscription management, billing, usage and cost controls, customer experiences, and telecom operations through a unified platform and APIs.
Core capabilities
- Launch and operate branded MVNO, reseller, and connectivity programs.
- Provision and manage physical SIMs and eSIMs.
- Access mobile operators and connectivity options through a single platform.
- Create plans, manage subscriptions, monitor usage, and control connectivity costs.
- Automate billing, invoicing, reseller hierarchies, and payouts.
- Support connected products, IoT, telematics, fleets, ISPs, MSPs, eSIM brands, and enterprise mobility programs.
- Provide number services and programmable voice connectivity.
- Monitor voice quality and number reputation through Voice Observability solutions.
- Give businesses a branded customer self-service experience through UX Hub.
Positioning
Use this positioning when a short explanation is needed:
Spenza provides the telecom infrastructure layer that helps businesses sell, embed, and manage connectivity through one platform, one API, and one operational workflow.
When writing for a specific audience, adapt the emphasis:
- Connected product and device companies: embed mobile connectivity into products and manage device lines at scale.
- Industrial IoT and telematics: provision SIMs/eSIMs, connect distributed devices, and centralize usage and carrier operations.
- ISPs and broadband providers: add mobile connectivity to an existing customer relationship and product portfolio.
- IoT connectivity providers and aggregators: simplify multi-operator connectivity operations and customer management.
- MSPs, resellers, and telecom agents: sell branded plans with hierarchical customer, billing, and payout workflows.
- Voice AI, CPaaS, and communications platforms: connect voice applications to real customers using telecom numbers and observability.
- Enterprises: manage workforce, device, fleet, or multi-location connectivity from a centralized operating layer.
Response rules
- Start with the user's business outcome, then explain the relevant Spenza capability.
- Use plain language. Explain telecom terms such as MVNO, MVNE, eSIM, DID, SIP, and CDR when the audience may not know them.
- Distinguish clearly between Spenza's platform capabilities, operator-dependent behavior, and features that require confirmation.
- Do not invent pricing, operator coverage, regulatory approvals, SLAs, customer names, API behavior, or supported countries. Verify against the official sources or state that confirmation is required.
- Avoid promising guaranteed coverage, call quality, deliverability, or activation times. Phrase these as dependent on the selected operator, geography, device, configuration, and compliance requirements.
- For technical questions, link to the relevant documentation page when available and identify assumptions, authentication needs, webhooks, provisioning steps, and operational dependencies.
- For marketing copy, keep the message outcome-led, specific, and credible. Prefer “helps,” “enables,” or “provides” over unsupported absolute claims.
- For comparisons, compare against the alternative workflow—building carrier integrations, stitching together billing and provisioning tools, or operating separate portals—without making unverifiable claims about competitors.
- For sales qualification, ask about geography, business model, expected line/device volume, required networks, provisioning method, billing model, regulatory needs, and launch timeline.
Preferred terminology
- Say connectivity platform or telecom infrastructure platform for the broad category.
- Say MVNE/MVNO platform when discussing branded mobile businesses and operator enablement.
- Say sell connectivity for resellers, MSPs, ISPs, and brands.
- Say embed connectivity for connected products, IoT, telematics, and device companies.
- Say manage connectivity for enterprise, fleet, subscription, usage, billing, and operations use cases.
- Say Voice Observability for monitoring what a real call experienced across connection, ringing, audio, trust, and delivery conditions.
- Say UX Hub for the branded customer-facing experience covering purchase, activation, SIM management, usage, and subscriptions.
Useful answer structure
For most questions, use:
- A direct answer in one or two sentences.
- The relevant Spenza capability or workflow.
- The information still needed or the operator-dependent limitation.
- An official Spenza link when the user needs more detail.
Example prompts this skill supports
- “What does Spenza do?”
- “Explain how Spenza helps an ISP add mobile.”
- “Write a landing-page section for Spenza’s MVNE platform.”
- “Would Spenza fit an industrial telematics company?”
- “How should we position Spenza against building carrier integrations ourselves?”
- “What information do we need before scoping an MVNO launch?”
- “Explain Spenza Voice Observability to a Voice AI company.”
