How things actually work

Talkala Help Center

This is where you find the real rules: how billing works, why a call might not start, what happens to your balance during a call, and the limits you should know about before you dial. No marketing gloss. Just how the product actually behaves.

The short version

Search by keyword or topic

Confirmed behavior vs. areas still under review

Direct links to rates, policies, and support

Search the rules

Search by question, keyword, or product area

Try terms like refund, caller ID, unsupported destination, or auto top-up.

31 answers

Quick index

Jump straight to the rule you need

31 indexed topics and answers

Account

Calls

Billing

Numbers

Caller ID

SMS

Limits & safety

accountConfirmed

What happens if a Talkala account is closed

A closed account cannot sign in to the product until admin reopens it. Reopening restores access only. It does not automatically restore released numbers or removed saved cards.

Closing an account is an admin action. Once the close succeeds, app access is cut off on the next server-side check and the account is sent to a dedicated `account closed` state after ownership is proven.

That is different from permanent deletion. Most accounts are closed and archived, not erased, because billing, call, messaging, and support history may still need to exist for operational records.

Closed accounts cannot reopen themselves from the sign-in screen.
The original email stays reserved. Signing up again with the same email does not create a fresh replacement account.
Support or admin can review the closure and reopen the account when appropriate.
Reopening restores access only. Released numbers and removed saved cards are not recreated automatically.
Permanent deletion is limited to truly empty test accounts with no meaningful product, billing, support, or provider-linked history.

closed accountreopen accountaccount accesssupport

accountConfirmed

Why some account emails and screens use generic wording

Talkala does not always confirm whether a specific email already has an account when you try to sign up, resend verification, or request a password reset. That is intentional.

This is a security feature, not a bug. If a site clearly tells anyone whether an email address already has an account, it makes account-enumeration attacks easier.

So Talkala uses neutral wording in a few account flows. You might see instructions like `check your inbox` even when the system is deliberately not confirming whether that email is new, already verified, or already attached to an account.

Some public account and contact forms can also ask for a quick security check before they send email or route a message. That extra step is there to slow down automated abuse, not to collect more personal data from you.

Sign-up can send you to the same next-step screen whether the email is brand new or already tied to an account.
Verification resend and password-reset requests can return the same success response whether or not an account was found.
Public sign-up, account-recovery, and contact forms can require a short bot check before submission.
If you already have access, use Sign in instead of repeating sign-up.
If you cannot access the account, use Reset password or contact support.

account securitysign upverify emailreset password

accountConfirmed

What are the password rules?

Your password needs to be at least 10 characters and include uppercase, lowercase, a number, and a symbol. That applies whether you're signing up, resetting, or changing it later.

Talkala uses the same password policy everywhere: sign-up, password reset, and in-app changes. And unlike some services that cap you at 16 characters from the early 2000s, Talkala lets you use long passwords and full passphrases.

There's one extra check. Before accepting a new password, Talkala screens it against a list of passwords that have already appeared in known data breaches. If yours shows up on that list, you'll need to pick a different one.

Minimum length: 10 characters.
Must include uppercase, lowercase, a number, and a symbol.
Long passwords, passphrases, paste, and password managers all work.
Passwords found in known breach databases are rejected.

passwordaccount securityreset passwordsign in

accountConfirmed

Why Talkala needs cookies and browser storage

Talkala uses cookies and browser storage to keep you signed in, remember your theme, and store app preferences. It's not tracking you for ads. But blocking this storage can break things.

Here's the important distinction: this storage keeps the app working. It's not following you around the web to sell you shoes. Talkala uses a mix of authentication cookies (so you stay signed in) and local browser storage (so your theme and layout preferences survive a page reload).

If you clear or block that storage, you might get logged out or lose your preferences. That's the tradeoff.

Session cookies keep you signed in between visits.
Theme and layout preferences are stored locally in the browser.
Vercel Web Analytics can count aggregate page views without adding third-party analytics cookies.
Clearing or blocking storage can reset preferences or break sign-in.
The public site does not use a separate advertising or retargeting cookie stack.

cookieslocal storagesign inbrowser settings

Cookie Policy Privacy Policy Contact

accountConfirmed

Can I delete notifications or clear them in bulk?

Yes. You can delete one at a time, clear all the read ones, clear everything, or just mark them all read and keep them visible.

Talkala doesn't force you to stare at a wall of old alerts forever. The notifications page has cleanup controls so you can get rid of the noise without accidentally nuking something you haven't read yet.

Opening an unread notification marks it as read (as you'd expect). If you want to clean up without opening each one, use the row delete button for a single item, or the bulk actions at the top of the inbox.

Delete removes one notification.
Clear read removes only notifications you've already seen.
Clear all removes every notification in the inbox.
Mark all read keeps everything visible but clears the unread badges.

notificationsinboxdelete notificationmark all read

Contact

accountConfirmed

What you agree to when you create an account

Creating an account means you agree to the Terms of Service and acknowledge the Privacy Policy. Both are linked directly on the sign-up screen so you can read them before you commit.

There's no separate checkbox to tick. Instead, the sign-up screen puts direct links to the Terms of Service and Privacy Policy right next to the account creation buttons. The idea is that you can actually read them before clicking, not just check a box you'll never look at.

That covers both email/password sign-up and Google sign-in.

Terms of Service covers service scope, billing rules, limits, and acceptable use.
Privacy Policy covers what account, billing, call, and messaging data Talkala processes.
Marketing consent is not bundled into basic account creation.
Essential cookies and storage are covered on the cookie and privacy pages.

termsprivacysign upaccount creation

callsConfirmed

What do I need before I can place a call?

A verified account, a destination with a published rate that's currently allowed, and usually enough balance for the temporary hold. The exception: one free 60-second test call for eligible new accounts.

Having an account isn't enough on its own. You still need to clear a few conditions before the dialer will actually connect you.

In practice that means: verify your email, add credit, and dial somewhere Talkala currently supports. The one narrow exception is a server-enforced 60-second free first minute for eligible zero-balance accounts that haven't topped up yet, on routes priced at $0.99/min or less.

Email verification is required before you can call.
Most calls require enough available balance to cover the temporary opening hold.
Eligible zero-balance accounts get one capped first minute (before any paid top-up) on routes priced at $0.99/min or less.
The destination must have a published rate and pass current policy checks.
One active call per account and rate-limit checks still apply, even on the free-minute path.

setupfirst callemail verificationwallet balance

How It Works Rates Contact

callsConfirmed

Why a call might not start

Talkala checks your balance, the destination, your account state, and anti-abuse rules before it ever dials. If something fails, the call gets blocked before a real phone connection is created.

When you hit dial, Talkala runs through the route, your account, and your wallet before handing anything to Twilio. If one of those checks fails, the call stops right there. No phone rings anywhere.

This is why two different numbers can behave differently even when your browser and microphone are working perfectly fine.

Not enough balance for the starting hold
The one-time free first minute was already used or the account no longer qualifies
The destination is priced above the $0.99/min free-minute ceiling
No published rate for that destination
The destination is temporarily listed as unavailable while coverage or operations review is in progress
Blocked prefix or destination country not allowed by current policy
High-cost destination that still needs your in-app confirmation
Current rate above the active policy cap
Another active call already tied to your account
Too many call attempts in a short window

blocked callunsupported destinationpolicy limithigh cost route

Rates Acceptable Use Contact

callsConfirmed

Why a country can stay listed as unavailable

Some destinations stay visible in the rate directory even when Talkala is temporarily not placing calls there. When that happens, the route shows Unavailable, the price is hidden, and the call is blocked before any real connection starts.

A listed destination is not always a callable destination. Talkala can keep a country visible while upstream coverage, carrier support, or an internal operations decision is still under review.

That status is deliberate. It tells you the route exists in the product, but Talkala is not taking live calls there right now. Because the route is not currently for sale, published pricing is hidden until the destination is reviewed and reactivated again.

Unavailable destinations stay visible so you can still find the route in the directory.
The per-minute price is hidden while the route is unavailable.
Trying to call an unavailable destination is blocked immediately before Talkala creates the real phone connection.
A destination can become available again later if upstream support returns and Talkala reactivates it with reconfirmed rates.

unavailable destinationcountry unavailablehidden pricingroute status

Rates Contact

callsConfirmed

The call failed before the phone even rang. What happened?

Sometimes Talkala approves the call, but the browser-side session drops before Twilio actually dials the other person's phone.

This is a different problem from a blocked route or low balance. In this case the app already said yes to the call, but something between your browser and the calling service broke before the real phone leg started.

The usual suspects: browser microphone permissions got revoked, a privacy extension or VPN is interfering with call traffic, or a browser-specific security feature is blocking web calling. The fastest way to narrow it down is to try a clean browser profile or a different supported browser.

For step-by-step microphone permission fixes, see Microphone access and troubleshooting.

Refresh the page and confirm microphone access is still allowed for Talkala.
Disable privacy, VPN, or ad-blocking extensions that might inspect or block call traffic.
Some VPN browser extensions can break web calling even when they look disconnected.
If it only happens in one browser profile, test in a clean profile or a different browser.
If the other phone never rang, the call almost certainly ended before the real phone connection was created.

browser callingmicrophoneextensionsprivacy settings

Browser Calling Contact Help Center

callsConfirmed

Microphone access and troubleshooting

Browser calling needs microphone permission for your Talkala tab. If access was blocked, you can usually fix it in the browser’s site settings, then reload the page.

Yes — in most cases you can restore it. Change the site permission from Block back to Allow (or Ask), then reload Talkala so the browser picks up the new setting.

If you are still stuck after trying the steps below, contact us with your browser and device (for example “Chrome on Mac” or “Safari on iPhone”) so support can narrow it down quickly.

In Google Chrome on desktop, use Settings → Privacy and security → Site settings → Microphone, or click the lock or tune icon in the address bar while you are on Talkala and adjust microphone access for this site. More detail: Google Chrome microphone help.

Fast fix: With Talkala open, click the lock or site icon in the address bar and set Microphone to Allow if you see that control. Then reload the tab.
If the control is not in the address bar, open your browser’s full settings and find Site settings / Permissions, then move Talkala off the blocked list for the microphone.
Chrome, Edge, or Brave (Chromium): Settings → Privacy and security → Site settings → Microphone — review the blocked list and set this site to Allow. Chromium browsers may also need a full browser restart after you change OS-level microphone privacy. Chrome help (Google)
Firefox: Settings → Privacy & Security → Permissions → Microphone — adjust the exception for this site or clear the saved permission so Firefox can ask again on reload. Firefox camera and microphone permissions
Safari on Mac: Safari → Settings (or Preferences) → Websites → Microphone — set Talkala to Allow or Ask. Safari websites settings on Mac
Still failing: Check operating system microphone privacy too — the browser can be blocked at the Mac or Windows level even when the site is allowed inside the browser.
iPhone / iPad (Safari): Settings → Safari → Microphone — set to Ask or Allow as needed, then return to Safari. Control hardware access on iPhone
Wrong input device: In your browser’s microphone settings, pick the correct default microphone if multiple devices are listed. Chrome device settings
Reset a stuck permission: Remove Talkala from the blocked / saved list, or clear the site permission entirely, then reload so the browser can prompt again. Firefox can clear per-site permissions from the address bar panel; Chrome documents resetting site permissions under Site settings. Firefox permissions · Chrome site settings

microphonebrowser callingpermissionsChromeSafariFirefox

Browser Calling Help Center Contact

callsConfirmed

Why your call ended earlier than expected

Talkala calculates the maximum affordable duration from your balance when the call starts. When that limit runs out, the call ends. It's prepaid behavior, not a bug.

This is how prepaid calling works. When the call starts, Talkala looks at your available balance and the per-minute rate, calculates the longest call you can afford, and uses that as a hard limit.

If you need a longer conversation, the balance has to cover it before you dial. Topping up after the call already started won't extend the limit on that call.

Call length is limited by what your balance can cover at the moment the call starts.
The cap uses the current published rate for that route.
Adding funds after the call begins does not extend the existing call's limit.

call endedcut offbalance ran outprepaid limit

Rates Help Center Contact

callsConfirmed

What happens if you navigate away during a call

Talkala warns you before you leave the dialer mid-call. If you confirm, the call ends first, then the navigation continues. If you stay, the call keeps going.

This exists to prevent accidental call drops. Click a sidebar link while you're on a call and Talkala will ask if you're sure. It won't try to keep the call running in the background while you browse other pages.

If you choose to stay, the call continues. If you choose to leave, Talkala hangs up the current call first, then takes you where you wanted to go.

Leaving the dialer during "Connecting" or "In call" requires confirmation.
That includes sidebar links, top-bar links, browser back/forward, and closing or reloading the tab.
Confirming the leave ends the call before navigation happens.
Staying keeps the call active on the dialer.

leave dialerdashboardwalletnavigationactive call

Contact Help Center

callsConfirmed

Why the rate might be higher when the line type is unclear

Landline and mobile rates can be different. Talkala checks the number type before the call, but if the type is still unclear, it uses the higher published rate and asks you to confirm before dialing.

In many countries, calling a mobile costs more than calling a landline. Talkala first checks the destination with provider lookup data. If that does not return a clear answer, it uses numbering-plan metadata when the number is unambiguously fixed-line or mobile.

When Talkala still can't confidently tell which type a number is, it defaults to the higher published rate rather than showing you a price that might be too low.

You'll see a confirmation before the call starts so you know exactly which rate and minimum hold apply to that attempt.

landlinemobilerate estimateline type

Rates Countries

callsConfirmed

How to read Talkala pricing benchmark claims

The benchmark page is proof, not a universal promise. It compares benchmarked route checks against published carrier rates, while your live quote depends on the current destination and line type.

Price benchmark page compares Talkala against published carrier rates on a checked research set. It is there to show that the savings claims are grounded in real source-linked comparisons, not to promise that every destination, every carrier, and every number type will land at the same multiple.

Your actual quote still comes from the live rate directory and the number you are trying to call. Mobile routes can price differently from landlines, and when Talkala cannot confidently resolve the line type before dialing, it uses the higher published rate instead of showing an estimate that might be too low.

The benchmark page uses benchmarked default-rate route checks. It is not every live Talkala route.
Claims like "about 4 in 5" and "150x" come from the benchmark research set, not from every possible route in production.
Your real pre-call price is the current published rate shown on /rates or in the dialer flow for that destination.
If the line type is mobile or unresolved, the live quote can be higher than a specific benchmark example.

benchmarkcarrier rateslandlinelive quotepricing claims

Price benchmark Rates Countries

billingConfirmed

How call billing works

Before a paid call starts, Talkala sets aside some of your balance as a temporary hold. Think of it like a restaurant pre-authorizing your card. After the call ends, Twilio reports the real duration, and Talkala settles the final charge.

Talkala doesn't just drain your balance the instant you press dial. In the normal flow, it first places a temporary reserve (reducing your available balance while the call is active), then settles the actual charge after the call finishes and Twilio reports how long it really lasted.

Billing rounds up to the next full minute. So a 2-minute-and-12-second call gets billed as 3 minutes. The rate comes from the published per-minute price for that route, not from your browser's timer or any partial-second estimate in the UI.

Before a paid call starts, Talkala temporarily holds part of your balance.
The hold is not the final charge. It just sets funds aside while the call is in progress.
Any unused portion of the hold returns automatically after the final charge settles.
The one-time free-minute path starts with no hold and a 60-second server cap.
Final duration comes from Twilio's status callbacks, not your browser.
Billing rounds up to the next full minute.

billingwalletholdcapturewhole-minute billing

Rates How It Works Refund Policy

billingConfirmed

How the free first minute works

New accounts with zero balance can place one free call, capped at 60 seconds, before their first top-up. But only on routes priced at $0.99/min or less.

This is a narrow launch offer, not an open-ended free trial. It only works while all of these are true at once: your available balance is zero, you've never completed a paid wallet top-up, you haven't already used the offer, and the route you're calling is priced at $0.99/min or less.

If the call connects, Talkala records the normal first-minute charge in the ledger, then offsets it with a matching promo credit so you pay $0. Because billing rounds up to the next full minute, even a short 20-second connected call uses the whole offer. If the call never connects at all, the offer stays unused for next time.

Only available before your first successful paid top-up.
Only available while your available balance is zero.
Only applies on routes priced at $0.99/min or less.
Call length is hard-capped at 60 seconds.
Even a short connected call under 60 seconds consumes the offer (because billing rounds up to one full minute).
The offer is consumed only when an eligible call actually settles as a billed connected call.
Email verification, one-active-call enforcement, destination policy, and rate limits still apply.

free minutefirst callzero balancelaunch offer

How It Works Rates Contact

billingSupport review required

What happens with failed, short, or interrupted calls

Final billing comes from what Twilio reports about the call, not what your browser saw. If a charge looks wrong, it goes through support review. There's no blanket automatic refund for every failed-call scenario.

If a call never really became a normal conversation (it dropped, barely connected, or had terrible quality), the final billing outcome depends on what Twilio's callback reports about the call lifecycle and duration.

Talkala doesn't currently offer a blanket self-serve refund or automatic quality guarantee for every failed, short, or poor-quality call. If a charge doesn't match what you expected, reach out to support with the timing and destination details.

Final settlement uses Twilio-reported duration, not your browser's timer.
There's no broad automatic refund or quality-based money-back promise for every failed-call scenario.
If the charge doesn't match what you expected, contact support with timing and destination details.

failed callshort callinterrupted callpartial charge

Refund Policy Contact Buy a Number

billingConfirmed

When does purchased credit show in my balance?

After Stripe confirms the payment. Not when you open checkout, not when you click pay, but when the confirmation comes back.

The wallet is ledger-based, so credit only appears after the payment confirmation path completes successfully. No confirmation, no credit.

If a top-up looks delayed, the checkpoint is Stripe's confirmation, not the moment you started checkout.

top-upwalletcreditStripe

How It Works Refund Policy Contact

billingConfirmed

Why auto top-up didn't fire immediately

Smart Auto Top-up doesn't charge just because your balance is already below the threshold. It triggers after a qualifying balance drop.

This catches people off guard if they turn on auto top-up while their balance is already low. It's not a one-time rescue charge. Think of it as a refill rule that watches for a qualifying drop in balance, not a rule that checks "is balance low right now?" once and fires.

If you enable it when you're already below the threshold, it waits for the next qualifying drop before it kicks in.

auto top-uplow balancewallet settings

Help Center Contact

billingSupport review required

How refund requests are handled

Refunds aren't self-serve. Top-ups, failed-call charges, quality complaints, and number subscription issues all go through support review.

Talkala treats wallet top-ups, usage charges, and number subscriptions as different kinds of charges, so the answer depends on what actually happened.

The rule today: review, not a blanket money-back guarantee. If you think you were charged incorrectly, contact support with the details.

refundbilling issuecharge review

Refund Policy Contact How It Works

numbersConfirmed

How dedicated numbers are billed

Two separate bills. The number itself is a recurring Stripe subscription. Receiving SMS on that number costs wallet balance per segment. One doesn't cover the other.

Your wallet covers prepaid usage like calls and inbound SMS. The number itself is a separate recurring Stripe subscription that keeps the number assigned to you.

At launch, owned numbers support inbound SMS in the browser. Each received SMS segment still costs wallet balance before Talkala accepts it.

These are intentionally separate. A healthy wallet balance doesn't pay your number subscription for you, and an active subscription doesn't waive inbound SMS charges.

Only plain-text inbound SMS is billable in this version. MMS with photos, videos, audio, contact cards, or other media is outside launch scope and doesn't create a wallet charge or inbox message.

The recurring number subscription and inbound SMS wallet charges are separate billing paths.
Inbound SMS is billed per received segment from prepaid wallet balance.
If the wallet can't cover the next inbound segment, the message is dropped instead of creating unpaid inbound usage.
Media-bearing MMS is not supported and doesn't create an inbound SMS charge or inbox entry.

phone numbersubscriptionwallet separationbilling

Buy a Number Terms of Service Refund Policy

numbersConfirmed

Can people call my Talkala number?

Not for voice. Not yet. Owned numbers currently support inbound SMS and outbound caller ID, but not inbound voice calls or voicemail.

This is an important limitation right now. Buying a number doesn't turn Talkala into a phone that rings in your browser when someone calls you.

Today, the number gives you two things: inbound SMS in the app, and the ability to use that number as your outbound caller ID (where supported). Inbound voice calls and voicemail are not active in this version.

Live now: owned numbers support inbound SMS.
Live now: owned numbers can be used as your outbound caller ID.
Not live yet: inbound voice calls to your browser.
Not live yet: voicemail.

inbound voicevoicemailphone numberfuture feature

Buy a Number How It Works Contact

numbersConfirmed

What happens when you cancel a dedicated number

The number is removed from your account and released immediately. The Stripe subscription is set not to renew at period end. Don't assume you'll keep access through the end of the billing cycle.

Here's the thing that trips people up: billing and access don't end at the same time. When you delete a number, the app removes and releases it right away. The Stripe subscription just gets flagged not to renew.

So if keeping the number until a specific date matters to you, don't delete it and assume you'll keep access until the billing period ends. Right now, deletion means immediate removal.

The number is removed and released immediately when you delete it.
The Stripe subscription is canceled at period end (no more renewals).
Don't rely on post-deletion access unless support confirms an exception.

cancel numbernumber releasesubscription end

Refund Policy Contact

caller idConfirmed

What number shows when you call someone

It depends on your setup. Talkala uses either your verified caller ID, your owned dedicated number, or a shared service number, depending on what you've configured.

If you care about whether the person you're calling picks up (and you should), caller ID setup matters. Someone is much more likely to answer a number they recognize.

When you haven't configured your own verified or owned caller ID, Talkala falls back to a shared service number where that path is available.

caller IDdisplay numberoutbound identity

Caller ID Buy a Number Contact

caller idConfirmed

What can block caller ID verification

Verification goes through Twilio's external validation flow. It can be rate-limited, and you can't add a number you already own inside Talkala as an external caller ID.

This isn't just a form you fill out locally. The verification depends on Twilio's external validation completing successfully, which means it can fail or get rate-limited for reasons outside Talkala's control.

One common stumbling block: if you already own a number inside Talkala, use it as an owned calling number. Don't try to re-add it as an external caller ID.

verify caller IDvalidation callrate limited

Caller ID Buy a Number Contact

smsConfirmed

How the SMS inbox is billed

Receive-only and text-only. Your phone number subscription renews separately, and each incoming SMS segment is charged from wallet balance.

The Messages page is an inbound inbox, not a general texting tool. Replies sent to your Talkala number can appear there, but outbound browser texting is still off at launch.

Launch scope is plain-text SMS only. If someone sends an MMS with photos, videos, audio, contact cards, or other file attachments, that message does not become an inbox thread.

Billing is split in two parts. Your dedicated number renews as its own recurring Stripe subscription, and each incoming SMS segment is charged from your prepaid wallet balance before Talkala accepts it.

Delivery also fails closed. New texts are dropped if the number subscription is inactive, the wallet cannot cover the next segment, inbound pricing for that number is missing, or the incoming message includes media instead of text-only SMS.

Receive-only inbox: no outbound browser texting at launch.
Text-only inbox: plain SMS can appear, but MMS with media does not.
Number subscription and incoming SMS charges are separate.
Incoming SMS is charged per received segment from wallet balance.
New texts are dropped when subscription, pricing, or wallet requirements fail.
Media-bearing MMS is outside launch scope and does not create an inbox message or wallet charge.

SMSinbox billingwalletnumber subscription

Buy a Number SMS From Browser Contact

smsConfirmed

How SMS works right now

Receive-only and text-only. You need an owned number in your pool. Talkala isn't offering outbound browser texting at launch.

The SMS inbox can only show messages for numbers it can confirm are yours. No owned number in your pool means no SMS thread.

At launch, the inbox is receive-only. You can see inbound texts tied to your number, but you can't send general outbound texts from your browser.

Launch scope is also text-only. Standard SMS can appear in the inbox. MMS with photos, video, audio, contact cards, or other media hits the webhook but gets treated as unsupported instead of appearing in your inbox.

Talkala doesn't currently publish a detailed destination-by-destination SMS coverage matrix the way it does for voice rates. So treat SMS as a narrower, more support-driven part of the product for now.

No owned number means no SMS inbox flow.
The launch inbox is receive-only, not an outbound texting tool.
Launch scope is text-only SMS, not MMS or media messaging.
Inbound SMS to an unknown or unowned number won't appear in the app.
Public SMS coverage details are more limited than the voice rates directory.

SMSmessagesassigned numbertexting

SMS From Browser Buy a Number Contact

smsConfirmed

Why an inbound text didn't show up in your inbox

Talkala only delivers a plain-text inbound SMS when the number is active, pricing is configured, and the wallet can cover the next segment. If any of those fail, the message is silently dropped.

The inbox fails closed at the prepaid and launch-scope boundaries. If the number subscription is inactive, pricing isn't configured, the wallet can't afford the next SMS segment, or the message contains media, Talkala acknowledges the provider webhook but doesn't create an inbox message.

That media rule is broader than photos alone. Videos, audio clips, contact cards, and other MMS-style attachments are also outside launch scope.

This is why a number can look like it's set up correctly but still refuse new inbound messages until the billing or configuration issue is resolved.

Low wallet balance drops the next inbound SMS instead of creating debt.
An inactive number subscription blocks inbound delivery.
Missing inbound SMS pricing blocks delivery until support fixes the configuration.
Media-bearing MMS is acknowledged and dropped without wallet charge or inbox entry.

SMSmissing messagelow balancenumber subscription

Buy a Number Refund Policy Contact

limitsConfirmed

Can I run more than one call at a time?

No. One active call per account. That's a product limit, not a bug.

This is intentional. If one call is already active on your account, a second call attempt will be denied. Finish or end the first call before starting another.

concurrent callsactive callone call at a time

limitsConfirmed

Can I use Talkala for emergency calls?

No. Absolutely not. Talkala cannot reach 911, 112, 999, or any emergency number. Use a real phone for emergencies.

This is a hard line. Browser-based calling cannot guarantee the connectivity, location accuracy, or emergency-service routing that a proper emergency-capable phone provides. If you need emergency services, use a mobile phone or landline.

emergency911112safety

Emergency Calling Terms of Service

Next step

Question about your specific account?

If the answer depends on a particular call, payment, number, or verification attempt (not a general product rule), start on the contact page. Signed-in users should use in-app support.

Contact Talkala

Check rates