Question 1

What is Akedly?

Accepted Answer

Akedly is MFA as-a-service that orchestrates fallback across multiple channels to deliver OTPs wrapped in a security layer that prevents attacks and fraud; built to generate revenue and cut down on attack induced bills.

The multi-channel fallback covers every use case so you don't lose users at sensitive points in your app, prioritising the highest possible success rate to prevent CAC and possible revenue loss.

The anti-fraud layers protect against attacks that don't just put your app at risk but your OTP bill with bot-induced OTP requests.

In action, those materialise in our 2 value propositions: reliability and security.

Question 2

Are you just an OTP sender? Can you issue me an SMS sender?

Accepted Answer

No. We're authentication-as-a-service, not an OTP vendor or a sender, and we cannot issue you an SMS sender as we are not a CPaas. All sending via SMS goes out under our own sender name, but the content of the message includes your company name.

Question 3

What's your value proposition?

Accepted Answer

Reliability and security to generate revenue and cut down attack induced OTP bills.

Reliability; making sure your customers actually receive the OTP via our orchestration algorithm which automatically prioritises the most reliable channels first, WhatsApp → Telegram → SMS, to reach your users with the highest success rate.

Security; making sure your API endpoint can't be spammed or attacked through granular rate limiting, device fingerprinting, captchas and more, so your bill does not spike with bot-induced OTP requests and your app remains secure.

All of this happens automatically; you don't have to change anything in the API.

Question 4

What do you mean by Reliability?

Accepted Answer

Revenue capture. Making sure your customers actually receive the OTP via our orchestration algorithm which automatically prioritises the most reliable channels first, WhatsApp → Telegram → SMS, to reach your users with the highest success rate. This maximises the authentication success rate so all possible channels your users are on is covered.

This way you do not lose your users at the most critical points in your flow, and no wasted CAC.

Question 5

What do you mean by Security?

Accepted Answer

Making sure your API endpoint can't be spammed or attacked through granular rate limiting, device fingerprinting, captchas and more, so your bill does not spike with bot-induced OTP requests and your app remains secure.

This not only protects your bills but also ensures only the correct user can authenticate successfully, without compromising your app.

Question 6

Why businesses choose Akedly?

Accepted Answer

We solve the problem of losing users to issues beyond your control, failed telecom infrastructure, late OTPs, or users who aren't reachable on the channel you chose.

Those users you worked hard for get lost right at your doorstep, during your most sensitive transactions, which means lost revenue.

We also protect you from attacks, so you don't get hit with an expensive bill or a server taken down through exposed APIs.

If you want to offload the hassle of making sure everything arrives on time and users aren't blocked at critical moments, we manage all of it, as best and as honestly as we can.

Question 7

How do you ensure reliability & security at Akedly?

Accepted Answer

1) Multi-channel orchestration, we automatically route across WhatsApp, Telegram and SMS to reach the highest deliverability rates.

Real results, we've taken customers' unique successful-authentication rates from as low as 20% up to 90%+.

2) Full customization, you customise the flow you need, the channels you use, and your quotation around your own customer base.

Tailor your experience to fit your needs, every business is unique.

3) A security-first, value-first approach, every integration is wrapped in security layers, so no bots get through and you never pay for fake users.

Most if not all our customers are inbound and suffered from $$$ pricey OTP bills due to bot-induced spam attacks. We actively enhance our security suite to protect you from this very spike. Your success is our success.

4) Recurring customers' best friend; using Passkeys enables you to cut down on time to authenticate by 4x (from 32 seconds to 8 seconds), using state of the art authentication (FIDO2 Compliant), up to 40% cost efficient vs OTP. Enroll your customer with OTPs once, and forget.

This maximises the unique user success rate and the security layer to give you the ultimate premium cycle for your users so you can focus on the rest of your user's journey in your app.

Question 8

Why should I choose Akedly?

Accepted Answer

If you want a premium channel that maximises: customer retention and revenue capture, reliability and deliverability, protection of your users, as fast  and as smooth as possible, that's us.

Question 9

How does Akedly compare to Twilio, Firebase or WhatsApp Business?

Accepted Answer

We do the heavy lifting and the defence for you. Twilio, Firebase and WhatsApp Business are senders, you wire up each one, manage failover, and handle security yourself. With Akedly you get multi-channel orchestration, automatic fallback, and our full security layer in a single integration, no expensive surprise bills and no unclear pricing. You can even bring your own SMS sender and keep your negotiated prices.

Question 10

Who is Akedly for?

Accepted Answer

Businesses that want to capture the revenue they earned, protect their app and their bills from attacks, and make sure their users actually convert at the most critical sensitive transactions and not fall through due to late or undelivered OTPs.

Question 11

Who should NOT use Akedly?

Accepted Answer

If you're just looking for a sender, to bulk-buy OTPs at a cheap rate, and don't care whether OTPs arrive or users convert; we're not for you.

Question 12

What's your vision? What do you believe in?

Accepted Answer

A value-first approach; your success is our success. We believe in working with our customers, which means maximizing your delivery and successful-authentication rate, and continuously shipping better tooling and features like passkeys.

Question 13

How do I get started?

Accepted Answer

It's simple: Integrate, Subscribe & go Live. Register here.

Question 14

How long does it take to start?

Accepted Answer

Ten to thirty minutes, depending on which API you use. We support RESTful integration, Widget integration, and you can even prompt your LLM with our docs to fast-track it.

Question 15

Do I need to pay before committing? Can I test for free?

Accepted Answer

Testing is 100% free. No payment before testing. You test first, always. We have a strict no-subscription-before-testing policy. Even if you wanted to pay immediately, we wouldn't let you until you've run our full cycle. That's how confident we are in what we offer.

Question 16

I'm still launching and have no traffic data. What should I do?

Accepted Answer

We love working with startups. Message us to get access to our special startup pricing.

Question 17

What other products do you have?

Accepted Answer

Continuously building and releasing products, such as Passkeys for recurring customers, Utilities which are business messaging such as payment confirmation, order tracking etc, and more. Register here to get early our latest product launches and features.

Question 18

How does pricing work?

Accepted Answer

Pricing depends on multiple factors:

1) Monthly/Annual OTP volume 2) Countries targeted 3) Channels used (WhatsApp, Telegram, SMS) 4) Vendors used (Twilio, Cequens, Firebase, etc.) 5) Methods used (OTP, Passkeys, TOTPs, Utilities) 6) API integration type (RESTful or Widget) 7) Type of financial commitment (Pay-As-You-Go, Annual, or Bulk Up-front)

All of this determines your rate. Rather than forcing a one-size-fits-all price, we look at where you are and work with you flexibly to generate the best quote for your stage and needs. Head over to Pricing to explore the ranges or request a quote.

Question 19

How do I get charged, per message or per successful authentication?

Accepted Answer

By default, Pay Per message. For enterprises, we offer Pay Per Successful Authentication. Check eligibility here.

Question 20

When do I get charged?

Accepted Answer

On WhatsApp and Telegram, when the OTP successfully delivers. For SMS, on sending. For passkeys, when the authentication goes through. You're never billed for checking multiple channels, only for the channel the OTP actually goes out on.

Question 21

What is Pay Per Message (PPM)?

Accepted Answer

You're charged per OTP that's sent (for SMS only) and delivered (for all methods).

Question 22

What is Pay Per Successful Authentication (PPS)?

Accepted Answer

You're charged only when your user actually completes authentication, not per OTP or per attempt. If a user requests 10 OTPs and only uses one, you're charged for that one. If they request several and use none, you're not charged at all.

Question 23

How can I be eligible for Pay Per Successful Authentication (PPS) billing model?

Accepted Answer

PPS is for enterprises. Three requirements: at least 30k OTPs per month, a high successful-verification rate for consecutive months, and implementation of our most secure APIs at time of subscription. Text the founders to discuss your eligibility and get a tailored quote.

Question 24

What are the ways I can subscribe?

Accepted Answer

Three options, each impacting your final OTP rate:

1) Pay As You Go 2) Annual Pay As You Go 3) Bulk Up-front

Question 25

What is Pay As You Go (PAYG)?

Accepted Answer

Pay As You Go (PAYG): flexible top-ups; charge your credit whenever you need to, however amount, at the default PAYG rates.

Best for early stage and low traffic.

Question 26

What is Annual Pay As You Go?

Accepted Answer

Annual PAYG: commit to a set OTP volume for the year, charge from the set volume flexibly, settle any leftover at the end of the year, and get exclusive rates for it.

Best for consistent traffic and our most recommended as it offers flexibility with discounted rates.

Question 27

What is Bulk Up-front?

Accepted Answer

Bulk up-front, our most exclusive rates, paid up-front for the credit you'll use.

Best for established high volume traffic to get most exclusive rates.

Question 28

How long do credits last?

Accepted Answer

12 months from purchase.

Question 29

Can I upgrade or switch plans? Am I locked in?

Accepted Answer

Yes, you can upgrade or downgrade anytime. No lock-in on anything, we're flexible. (Special packages may be an exception.)

Question 30

Why isn't there a single flat price?

Accepted Answer

Because your real cost depends on how you send. A WhatsApp OTP to Egypt and an SMS to Germany have very different underlying carrier costs, so instead of averaging everything into one misleading number, we price each channel, country, provider and volume band transparently.

Question 31

What currency are the rates in?

Accepted Answer

Listed rates are in USD. EGP applies only to local channels delivering to local users.

Question 32

Do rates change over time?

Accepted Answer

Carrier and provider costs move, especially for SMS. Committed plans lock your rates for the commitment term (still subject to our T&Cs), so you're insulated from mid-term changes.

Question 33

How do I get an exact quote for my app?

Accepted Answer

Request a quote or text us with your channels, destination countries and monthly volume, and we'll come back with a tailored price.

Question 34

What channels and vendors do you support?

Accepted Answer

WhatsApp, Telegram, Twilio (SMS), Cequens (SMS), and Firebase (coming soon), plus Email. We send wherever our vendors can cover, check the per-country table to see which vendors apply in each country.

Question 35

Why do only some SMS providers show for a country?

Accepted Answer

The rate table only shows providers that can actually deliver to the selected country, so you never see a rate you can't use. Twilio, Firebase and Cequens each cover different markets. Check the per-country table.

Question 36

Do you send globally?

Accepted Answer

Yes, wherever our vendors can cover. Check the per-country table to see which vendors apply in each country.

Question 37

What is the success rate?

Accepted Answer

Our verification success rate is 90%+ using our full multi-channel fallback and security layers.

Question 38

What is unique user success rate, and why does it matter?

Accepted Answer

Our unique user success rate is 85%+. It's the share of distinct users who actually complete authentication, not raw message counts. A single user often needs multiple OTPs or resends, so per-message success (90%+) runs higher than per-user completion (85%+). Unique user success rate is the metric that matters most, because it measures the real outcome: actual users getting through your flow.

It's the harder metric and the most relevant, and what we optimise for.

Question 39

How much load can you handle?

Accepted Answer

Text us to know more, for certain use cases, we build a custom environment for you.

Question 40

What is fallback?

Accepted Answer

Fallback means we check whether your user exists on a channel, WhatsApp, for example. If they don't, instead of you losing that customer forever, we fall back to the next channel in your stack (usually SMS or Telegram). We check whether the user exists there and route accordingly.

Question 41

When does fallback trigger?

Accepted Answer

When the user doesn't have an existing account on the vendor, except for SMS, which can't be detected that way.

Question 42

Can I use SMS as a fallback? Can I use SMS only?

Accepted Answer

SMS is hard to detect delivery on, so we always recommend placing it as the last fallback or as a standalone channel. Yes, you can use SMS only. You can also layer other channels on top of SMS, which is not just more effective but more cost-efficient, since SMS is usually pricier than other channels.

Question 43

Can I bring my own provider / sender / account?

Accepted Answer

Yes. We work with whatever stack you have, your own WhatsApp sender, your own SMS sender, or just bring it in and we'll handle fallback, passkeys authentication and security on top.

Question 44

Can I bring my own sender name?

Accepted Answer

Yes.

Question 45

Can I connect my own WhatsApp account?

Accepted Answer

Yes, we're official Meta Tech Providers so we can connect yours or issue you a new one.

Question 46

My app uses [X]. Do you support it?

Accepted Answer

We support as much as possible. Check our docs, and if you have a specific request, text us , our team moves fast to support new use cases.

Question 47

How do you protect against attacks?

Accepted Answer

We have 8 anti-fraud security layers, including but not limited to device fingerprinting, CAPTCHAs, granular rate limiting, and more. Continuously improving, we also run AI analytics on your traffic to recommend the best rate limits relative to your users' behvaiour.

Question 48

What is granular rate limiting?

Accepted Answer

Every business and its user behavior is different, so instead of generalising, you choose your own limits, per IP, per phone number, per minute, per hour, whatever fits your traffic. We also run AI analytics on your traffic locally and recommend the rate limits best suited to your users' behaviour because every business is unique.

Question 49

Do CAPTCHAs show on my frontend?

Accepted Answer

Depending on your implementation, we offer both options. User experience matters to us, so we have RESTful implementations to run CAPTCHAs in the background and design them to deter attackers without disrupting real users.

Question 50

What is opt-in?

Accepted Answer

For GDPR-compliant companies, opt-in means the user consents to receive an OTP.

Question 51

What is TOTP?

Accepted Answer

Time-based One-Time Passcode, which is a code is generated on an auth app like Google Authenticator, Apple Passwords etc, that is auto generated every 30 seconds.

Question 52

Do you monetize on my app getting attacked?

Accepted Answer

We design our security to minimise your app getting attacked as much as possible. For customers on Pay Per Successful Authentication (PPS) billing, we don't charge for failed authentications nor for attack-induced OTP requests. For customers on Pay Per Message (PPM), we do our best to shield you from attacks with the latest security upgrades in our APIs, but do not take responsbiliy for it.

Question 53

What are passkeys?

Accepted Answer

Passkeys are a passwordless authentication method built on the FIDO2 and WebAuthn standards. Instead of sending a code, the user authenticates with the biometrics or PIN already on their device (Face ID, fingerprint, etc.). A cryptographic key pair replaces the password, the private key never leaves the user's device, so there's nothing to intercept, phish, or leak. That makes passkeys phishing-resistant and eliminates the delivery-failure and interception risks that come with OTPs entirely.

Question 54

Where do you store the passkeys?

Accepted Answer

We don't store them. The passkey lives on the phone itself, secured by the device's own biometrics (Face ID, fingerprint). Since authentication happens through the phone's biometrics, the private key never leaves the device, only a public key is ever shared, so there's nothing on our side to store, intercept, or leak.

Question 55

I want to secure sensitive transactions but not send OTPs, can I?

Accepted Answer

Yes. Passkeys are built for exactly that, strong authentication with no message to deliver. The one exception is enrollment: each user verifies with a single OTP the first time, to prove they own the account, then registers a passkey. After that, every future authentication uses the passkey, with no OTP to send.

Question 56

Why should I use passkeys?

Accepted Answer

4x faster than OTPs, up to 40% cheaper, and FIDO2 compliant; the most secure authentication method available. Passkeys are phishing-resistant, and eliminate the delivery-failure and interception risks that come with OTPs entirely.

Question 57

Who are passkeys for?

Accepted Answer

Enterprise. If you're an enterprise, email us or text us to request access.

Question 58

What is a WhatsApp Business account?

Accepted Answer

It's a dedicated account we create for you as a Meta Tech Provider, with your brand name, and logo, through which you send OTPs, Utility messages, and more.

Question 59

Can you issue me a WhatsApp Business Account?

Accepted Answer

Yes. As official Verified Meta Tech Providers, we can issue your business a WhatsApp Business Account. Head over to our dashboard to apply for one using our 5-minute wizard.

Question 60

How do I get a WhatsApp Business account?

Accepted Answer

Go to your dashboard, open WhatsApp Setup, complete the 5-minute wizard, and upload your company documents so Meta can verify you. Meta typically responds within 14 business days.

Question 61

Why should I use WhatsApp with Telegram/SMS fallback?

Accepted Answer

It maximizes reliability, and you're only charged per channel the OTP actually goes out on, not for checking across channels.

Question 62

Are you a Meta Business Partner? What does that mean?

Accepted Answer

Yes. It means we can onboard you with your own WhatsApp account, and you get priority support for any issues you face through us.

Question 63

Does the WhatsApp account require documentation?

Accepted Answer

Yes, company documents are required for Meta verification.

Question 64

What are your compliances / certifications?

Accepted Answer

Check it out here, or message us for the full, detailed list of our security and compliance posture.

Frequently Asked Questions

Why Akedly

Getting Started

Pricing & Billing

Channels & Coverage

Fallback

Bring Your Own

Security

Passkeys

WhatsApp & Meta

Compliance & Reliability

Legal & Refunds

Support