Frequently Asked Questions

Contact us with your target countries, expected traffic volumes, use case, and integration requirements. Our team will help design the appropriate messaging setup and onboarding plan.

Onboarding timelines depend on the integration complexity and any required registrations. Standard OTP and transactional messaging setups can often be launched quickly, while regulated markets may require additional approval processes.

Yes. We offer standard onboarding configurations based on common industry practices, especially for OTP and transactional messaging use cases.

Yes. Every customer has different requirements. We configure routing, compliance, and operational settings according to each customer's traffic profile and business objectives.

Yes. For key customers, reporting can be customized to align with specific operational, commercial, or compliance requirements. Custom reporting formats, delivery metrics, traffic breakdowns, and data views can be discussed and configured individually as part of the ongoing partnership. The scope of customization depends on the use case, traffic profile, and reporting objectives, and is reviewed together with the customer during the onboarding process and throughout the cooperation.

Contact us through our website and include the event name, location, and preferred meeting dates. We will coordinate with the appropriate account representative.

Yes. Customers can integrate with Scarpel Telecom through API, SMPP, and webhook-based workflows. Our platform can be connected to CRMs, customer engagement platforms, backend systems, mobile applications, and internal business tools. For customers who do not require development work, we also provide a self-service customer portal for campaign management and reporting.

Yes. Our SMS platform provides API connectivity for sending messages, receiving delivery reports, monitoring traffic, and integrating messaging into existing applications and workflows.

Yes. We support SMPP connectivity for customers requiring high-volume messaging, direct telecom integrations, or enterprise-grade messaging workflows.

Yes. Webhooks can be used to receive delivery reports, message status updates, and other event notifications in real time.

Not necessarily. Technical teams can integrate through API or SMPP, while non-technical users can use our customer portal to launch campaigns, monitor delivery, and manage messaging activity.

Yes. Our customer portal allows users to send SMS campaigns, monitor delivery performance, access reporting, and manage messaging activity without building a custom integration.

It depends on your use case. API integration is typically preferred for applications and automated workflows, SMPP is often used for high-volume messaging environments, while the customer portal is ideal for teams that want to manage campaigns without development work. Contact us and we will advise you on the best way to get started sending bulk messages for your particular case.

Yes. Delivery reports can be returned through supported integration methods, including API, SMPP, and webhook-based workflows.

A2P SMS allows businesses to send automated messages directly to mobile users. It is widely used for authentication, notifications, reminders, alerts, customer engagement, and transactional communications.

Our A2P SMS platform supports secure delivery of verification codes, login confirmations, transaction approvals, password resets, and other authentication-related messages.

Yes. OTP delivery is one of the primary use cases supported by our platform.

Yes. Promotional and marketing traffic can be supported where local regulations and operator policies permit such traffic.

Yes. Our platform supports multilingual messaging and international character sets.

Yes. Messages can be localized to improve customer engagement and user experience in specific regions and markets.

Yes. SMS delivery is independent of operating system and works across iOS, Android, feature phones, and other mobile devices connected to carrier networks.

A2P SMS is the communication channel. OTP is one of the many use cases delivered through A2P SMS.

We recommend separating transactional and promotional traffic because many operators apply different filtering and compliance rules to each traffic type.

Customers can access delivery reports, message statistics, route performance data, and operational metrics through available reporting tools and integrations.

Most messages are delivered within seconds. Actual delivery times depend on destination networks, operator processing, coverage conditions, and local regulations.

We provide international coverage through operator and aggregator partnerships across multiple regions worldwide.

We continuously monitor route quality, delivery performance, and operator connectivity to maintain reliable message delivery.

Internal monitoring systems track delivery performance, route stability, and traffic behavior. Quality alerts help our operations team investigate potential issues.

Delivery reporting is based on status information received from operators and downstream networks.

The exact meaning depends on the operator and country. Delivery reports indicate successful processing according to the status information returned by the network.

No provider can reliably guarantee handset-level delivery in all markets because delivery reporting depends on operator infrastructure, device behavior, network conditions, and local implementations.

For customers, Delivery Ratio is calculated as: Delivered Messages ÷ Messages Submitted to Scarpel Telecom. This represents the percentage of messages successfully reported as delivered by downstream networks.

In many countries, delivery reports are generated by network infrastructure rather than the handset itself. Therefore, no provider can reliably prove that a message was displayed on a user's device in every market.

Reporting typically includes delivery statistics, delivery status information, traffic metrics, and operational performance data.

Our monitoring systems detect abnormal performance changes and trigger internal investigation processes to identify and address quality issues.

LCR (Least Cost Routing) is used only in specific routing products, primarily within wholesale environments where cost optimization is required.

Deliverability depends on local operator policies, anti-fraud systems, sender ID requirements, regulatory frameworks, and network infrastructure.

We operate a secure messaging environment with controlled access policies, operational monitoring, and protected connectivity options.

We use anomaly detection, traffic analysis, route monitoring, suspicious-pattern detection, active route testing, and number-range filtering to identify and mitigate fraudulent activity.

No. Fraud protection is integrated into the messaging platform and enabled for all customers.

Yes. We assist customers with sender ID registration, content approval, and other market-specific compliance requirements where necessary.

Yes. We guide customers through country-specific sender registration, content registration, and operator compliance processes.

No. We never sell, share, rent, or provide access to client databases or customer data to third parties. Data security and confidentiality are fundamental principles of our business. All client information is handled in accordance with strict security and privacy standards, and is used solely for the purpose of delivering the agreed services.

Pricing is determined by destination, traffic profile, message type, and routing requirements.

Commercial terms depend on the customer's requirements and traffic profile. Flexible engagement models are available.

Yes. Pricing can be adjusted based on traffic commitments and long-term partnerships.

The primary factors are destination country, traffic volume, route type, and compliance requirements.

We focus exclusively on A2P messaging, providing tailored routing, flexible commercial structures, direct operational support, and customer-specific solutions.

No. We do not require any minimum monthly revenue or traffic commitment. Whether you're launching your first OTP flow, testing a new market, or sending millions of messages per month, you can start with the volume that fits your business needs. This flexibility makes Scarpel a preferred SMS provider for startups, fintech companies, iGaming operators, CPA networks, SaaS platforms, and enterprises looking to test SMS delivery before scaling.

Yes. We accept cryptocurrency payments, including USDT (TRC-20), making it easier for international businesses, iGaming operators, crypto platforms, and companies in restricted markets to fund their SMS campaigns quickly and efficiently. Crypto payments are processed securely and provide a convenient alternative to traditional bank transfers.

Yes. We offer testing opportunities that allow prospective customers to evaluate SMS delivery quality, route performance, delivery reporting, and platform capabilities before committing to larger volumes. Testing is especially valuable for businesses sending OTP, transactional, promotional, or high-volume A2P SMS traffic, as it provides real-world visibility into delivery performance in their target markets. Our team will recommend the most appropriate testing approach based on your destinations, traffic type, and business requirements.

We work with fintech, banking, e-commerce, iGaming, ride-hailing platforms, SaaS, logistics, healthcare, travel, telecom, and other businesses that depend on reliable messaging.

Our customers range from startups and growing technology companies to enterprise organizations and wholesale telecom partners.