Talkala Help Center

This applies to gmail.com and googlemail.com addresses. Your submitted address keeps its dots and +label for display and email. Other email providers and custom Google Workspace domains can treat dots differently.

If signup reports that this Gmail inbox is already in use, sign in using the address you originally registered, or choose Recover access and enter that exact address. Recovery sends a reset link to the address on the account. Only someone who opens that link can set a password.

If you already have several accounts using variations of the same Gmail address, keep using each original address. Accounts, balances, and call history are not merged. Recover each with its exact registered address, or contact support if you cannot remember it.

A dot or plus sign does not mean someone has abused Talkala. If your account is closed, contact support about reopening access.

Opening the form does not save a contact. You can change the name, country prefix, phone number, company, email, website, tags, notes, favorite status, and contact photo before saving. Cancel leaves the saved contact unchanged.

To change an existing contact, open Contacts, select the person, and choose Edit. Each contact has one phone number. A number cannot be saved twice in the same contact list.

For a contact photo, choose Upload Photo, adjust the crop, and apply it. Use an image up to 6 MB and 24 megapixels, with no side over 8,192 pixels. Save Contact keeps a small square version with the rest of the changes. The original file is not kept. Choose Remove to remove the contact photo, then save the contact to keep that change.

Personal and team contact lists are separate. On Team Phone, Save contact opens that team's contact form. Owners and admins can manage shared contacts; callers can search and call them. Team contact notes are visible to team members.

Copying personal contacts into a team reads the personal list in batches and skips numbers already in the team. A copied contact is independent of its personal original. CSV export includes the contacts matching the current search and filter. Import skips duplicate numbers and invalid rows. If an import stops partway through, already saved contacts remain; reload the list before retrying the file.

Talkala support handles account closure. After an account is closed, it cannot open the app again unless support reopens it.

Before closing access, support must resolve active calls, automatic charges or billing work, active team ownership, positive wallet balance, and any number cleanup still in progress.

Closing an account is not the same as deleting it. Billing, calls, messages, numbers, support, and audit history can remain for billing integrity, disputes, abuse prevention, or legal duties. Privacy erasure is a separate verified request.

This is intentional security behavior. If Talkala clearly confirmed whether an email has an account, attackers could use that answer to guess who uses the product.

Some account screens therefore use neutral wording. You might see `check your inbox` even when Talkala is not saying whether the email is new, already verified, or already attached to an account.

Some public account and contact forms can also ask for a quick bot check before sending an email or message. That step slows automated abuse. It is not there to collect extra personal data.

Talkala can also temporarily stop new account creation when many accounts appear to come from the same source, or when the request does not provide enough basic source signal to apply that protection safely.

A temporary or disposable inbox is made for short-term use, shared through a public inbox, or issued by a service whose addresses are not meant to stay with one person. You may lose access to it, so it cannot reliably support account verification or recovery.

When you create an account, Talkala checks the email domain against known disposable-email domains. A match is rejected before an account or verification email is created. The same check applies when an unverified email/password account asks to change its email. A known temporary-email service can remain blocked while it is inactive.

This rule helps limit repeated claims of Talkala's free 1-minute call. It is an abuse-prevention measure, not a claim that everyone using a temporary inbox is acting improperly.

Use a permanent address you can access later. Custom domains and privacy-preserving aliases are supported when the address is not identified as a disposable inbox.

A permanent email address does not by itself guarantee the free minute. Account, destination, and offer conditions still apply.

If a legitimate address is rejected, contact support while signed out at Contact support. Tell us the affected domain and how you use it. Never send your password.

If you corrected an unverified email address, sign in with the corrected address and your existing password. To use Google, choose the Google account with that exact current email address.

The old email address cannot open the corrected account through Google. An existing Google session using the old address will be signed out when Talkala checks it again.

If Talkala cannot confirm that your Google account matches, sign-in stops. Try again when the service is available, or use your current email and password. Contact Support if the problem continues.

Some people start with Google sign-in and later prefer to sign in with an email password. Talkala uses the password reset flow for that change.

Enter the same email address on Reset password. If that email belongs to a Talkala account, the email link lets you choose a password. After that, you can sign in with email and password instead of Google.

For security, the reset screen still uses generic wording. It does not confirm whether a specific email exists.

Talkala uses the same password rules for sign-up, password reset, and in-app password changes. Long passwords and passphrases are allowed.

Before accepting a new password, Talkala also checks whether it has appeared in known data breaches. If it has, you need to choose a different password.

Changing or resetting an email password signs out existing email/password sessions. Sign in again with the new password on each device. Google sessions are not affected by an email-password change.

Talkala uses this storage to keep the app working. Authentication cookies keep you signed in, short-lived cookies support policy acceptance and protect access to staff-only tools, and browser storage remembers settings such as theme, layout, profile, and country preferences.

The public site does not use advertising or ad-tracking cookies. Vercel provides cookie-free aggregate traffic measurement. Google Analytics loads only after you choose Accept in the privacy banner, with advertising storage and personalization disabled. If Cloudflare Turnstile is configured, public and account-security forms can also use it for bot checks.

If you clear or block required storage, you may get logged out, lose saved preferences, interrupt Google sign-in when returning from Google's page, or fail a bot check on a form.

Open Settings, then Change avatar. Select a portrait and choose Save avatar, or open Upload photo to choose an image, adjust the crop and zoom, and choose Save photo. Reset crop recenters the photo and returns zoom to 100%. These changes save separately from your other preferences.

If you sign in with Google, your Google photo is used until you choose a Talkala avatar or upload a photo. Reset avatar or Remove photo clears only your Talkala choice. It does not change your Google account photo.

The notifications page has cleanup controls for old alerts. You can remove one notification, clear only the ones you have already read, or clear everything.

Opening an unread notification marks it as read. If you want to clean up without opening each one, use the row delete button or the bulk actions at the top of the inbox.

Email/password accounts get a verification email first. Talkala sends the welcome email only after that email address is verified. Google sign-up uses Google's verified email status, so the welcome email can be sent when the Google account is first created.

Notification emails follow your Settings at the time the event happens. If email alerts are off for that category, Talkala does not send the email later. If alerts are on, Talkala can email you about wallet top-ups, referral rewards, Smart Auto Top-up results, received SMS billing issues, number events, expiring saved cards, and failed calls.

Referral reward emails may include the invited user's display name or masked email so you can recognize which invite paid out. They do not include the invited user's payment amount, card, or payment details.

Notification emails include a footer link back to Settings so you can manage notification email categories. The first-signup welcome email does not include that notification settings link.

Some events stay in the in-app notification inbox only. Completed calls, accepted SMS, browser-call outcomes for calls to your Talkala number, and number release/removal notices are in-app only and are not sent by email.

There is no separate checkbox. The sign-up screen links to the Terms of Service and Privacy Policy next to the account creation buttons so you can read them before you create an account.

That covers both email/password sign-up and Google sign-in. Talkala stores the accepted Terms version, Privacy Policy version, acceptance time, and source so support can tell which policy set applied when the account was created or continued.

When you try to make a call, Talkala can keep technical details such as your browser version, broad device type, operating system, connection warnings and available audio-quality measurements. Incoming calls can also provide these details when you answer in the browser.

These diagnostics do not record what you say, create a transcript or identify your device across websites. They support troubleshooting and do not set your call charges; billing follows the calling network's confirmed records.

Some browsers provide fewer details, and a closed tab or lost connection can prevent a diagnostic update from arriving. Missing measurements do not prove that a call was clear. If you contact support, include when the problem happened and what you heard.

Optional browsing analytics are separate and follow your Cookie settings. Read the Privacy Policy for the categories of records Talkala keeps and why.

After a connected outbound call ends, the dialer may show a short question about the call. Choose the answer that best matches what you experienced, or close the question without answering.

The question is available only after Talkala confirms an outgoing call connected and ended. Incoming and unanswered calls do not get this question. You can submit one answer per call; answering is optional and does not delay your next call.

The choices describe your experience, such as good, poor sound, not hearing the other person, the other person not hearing you, or a disconnected call. Talkala does not ask for a written comment and does not record the conversation through this question.

Your answer is stored with that call so Talkala can compare what people experienced with available technical call-quality measurements. A missing answer is treated as unknown, not as a good call. Feedback does not change call charges, billing, or call history.

The tutorial shows the Phone screen, adding credit, choosing a country, entering a number, checking the rate, allowing microphone access, and using Mute and Keypad.

After ending the call, it shows the duration and cost summary, then opens call history for more detail. The account, number, rate and balance in the video are examples; check the values shown in your own account.

Having an account is only the first step. Before the dialer can connect, you need to verify your email, allow microphone access, and dial a destination Talkala supports.

Most calls also need wallet balance. The limited exception is the free first minute: qualifying accounts with no available credit that have not topped up yet can place one 60-second call when that call's price is $0.99/min or less.

The rate can depend on the caller ID used for the call. The public rate directory shows the default published catalog; the signed-in dialer confirms the actual rate for your selected caller ID before dialing.

On route pages with a published price, the optional field is for the destination number you want to call, not your own number. Set up your call opens the public Talkala phone with that destination and number ready. You can leave the field empty to explore, or edit the number using the phone input and keypad. Create account to call and Sign in both keep your latest edits. Signed-in visitors go directly to the authenticated phone.

When +1 is selected, enter the recipient's three-digit area code and seven-digit local number: ten digits in total. The shared +1 calling code does not replace the area code. Country-code guides show destination-specific area codes where verified; keep the code belonging to the recipient's number when several apply. You can also paste the complete international number. Talkala does not insert an area code for you.

For Spanish geographic numbers, keep all nine national digits after +34; do not add a domestic 0. The Spain prefix guides cover selected prefixes for Sevilla, Granada and Asturias, so an unlisted prefix can still be valid. Their approximate maps describe numbering zones, not the caller's current location or whether a particular number can be reached. A three-digit prefix alone may not establish the service type; enter the full number to check the rate.

It is not an open public dialer. Talkala does not request microphone permission, create a browser-calling session, reserve wallet balance, or place a phone call from that preview page.

Talkala keeps one prepared call in this browser for up to one hour, using a random reference in navigation links rather than putting the number in the link. Verification can open in another tab of the same browser and site. A new setup replaces the previous draft; entering the authenticated phone consumes it. If you switch browsers, clear or block site storage, or return after expiry, you may need to enter the number again. Nothing dials automatically. Published prices are starting rates; the authenticated phone confirms the full-number price and applies the normal account, trial and balance checks.

If you need to verify your email, the verification link keeps that destination for when you sign in. A new link requested from the verification screen keeps it too.

If Phone says calling is temporarily unavailable: Follow the current service notice. Adding credit or changing your microphone settings will not resolve a service-wide interruption. You can still check your balance and call history.

If there is no service interruption shown: Read the message for your attempted call. Check that your email is verified, microphone access is allowed, and the full destination number has an available rate. Most calls also need enough balance; the free first minute has separate eligibility rules. See what you need before calling.

A notice disappearing does not by itself prove that a call will connect. The dialer still checks your account, destination, and available balance before starting a call.

If the message is unclear or the problem continues, contact support with the message you see and the approximate time of the problem. Do not add more credit unless the dialer specifically says your balance is too low.

Talkala may show a notice across signed-in pages or only on Phone. It can share general information, a warning, or an urgent update.

Some notices can be dismissed. Your dismissal applies only to that version; if Talkala publishes changed information, the new version may appear again.

A service notice is an explanation, not a service control. Hiding or dismissing it does not enable calling, change a rate, spend credit, or alter your balance.

If calling is paused, Phone can keep showing a basic non-dismissible safety notice even when another notice is switched off or dismissed. That safety message remains until Talkala verifies that calling is available again.

When you hit dial, Talkala checks the destination, your account, and your wallet before creating the real phone connection. If one check fails, the call stops before any phone rings.

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

If you hear "Calling is currently unavailable for this account," check the message in Phone or contact support. That message does not mean another call is still open. "Another call is already active" is a separate message for an existing call.

A listed destination is not always available for calling. Talkala can keep a country visible while coverage, carrier support, or a service review is still in progress.

Unavailable means the country stays listed, but Talkala is not taking live calls there. Pricing stays hidden until the destination is reviewed and made available again.

If the message says calls to the destination are restricted, retrying the same number is unlikely to help. A restriction can apply to a particular number or range; it does not necessarily mean the whole country is unavailable.

If the number could not be reached through Talkala, check the full number, including the country code. Even a correctly formatted number may not be supported by the calling network.

If the message specifically identifies a browser connection problem, check your connection and microphone access. A privacy extension, VPN, or browser setting may interfere with web calling. Test a clean browser profile if the problem continues.

When the cause is unknown, Talkala shows a general failure message. A phone not ringing does not by itself tell us what failed. Check History for the final call status and charge; calls that never connect have no call charge.

For microphone permission fixes, see Microphone access and troubleshooting.

Can I check my microphone and sound before calling? On the idle Phone page, choose Test mic & sound below Calling from, or in the lower area below the call button on a narrow screen. Opening the check does not turn on your microphone or play sound. Select Check microphone, allow access if asked, then speak and watch the level. Select Play test sound and check that you can hear the ringtone, which repeats for up to 10 seconds; Stop test sound stops it immediately. The check is optional and does not place a call, record or upload your voice.

Which microphone and speaker does the check use? It uses the same browser and device defaults as ordinary calls. Use your phone or computer’s audio controls to change them, then check again. Talkala does not offer device selection in this check. Changing a headset or output later can change where your next call’s sound goes.

What does a successful local check prove? A microphone level can show local input, and hearing the test sound confirms that you heard local playback at that moment. Quiet input alone is not failure. This does not check the phone network or guarantee call quality. Closing the check, hiding the page, leaving Phone or a call starting/ringing stops its microphone check and test sound; browser permission may remain allowed.

How do I allow the microphone? Select Enable microphone on Talkala’s Phone page, or start a call and allow access when your browser asks. Mic Allowed means permission is available. Mic Ready means Talkala has opened the microphone and it is ready to use.

What if the microphone is blocked? Open your browser’s permissions or site settings for Talkala and allow microphone access. Some phones also have a microphone permission for the browser in the phone’s Settings app. The menu names vary by browser and phone. If a call is still active, end it before reloading Talkala and trying again. Pressing Enable microphone repeatedly cannot override a saved Block setting.

Can I switch between headphones and my phone during a call? Use your phone’s audio controls. Talkala gives a brief microphone change a moment to settle before showing a warning. If you can still hear each other, keep talking. If a microphone warning remains or the other person cannot hear you, check the selected input and use Check microphone when offered.

What if no microphone is available? Check that your microphone or headset is connected. If another app is using it, close that app and try again. Use Check microphone if Talkala shows that action. If it remains unavailable during a call, end the call before starting another.

What if the other person cannot hear me? Check that the call is not muted and that your headset is connected. Speak and ask them to confirm. A quiet sound indicator by itself does not mean the microphone is broken.

What if I cannot hear the other person? Check your volume and the phone or computer’s audio output. Sound may still be going to headphones or Bluetooth. Reconnect your headset if needed and select Enable sound when Talkala offers it. Where Talkala cannot offer an audio-device selector, use your phone or computer’s own controls.

What if an incoming call appears without a ringtone? Check your volume and audio output, then select Enable ringtone if Talkala offers it. If Safari on Mac still stays silent, open Safari’s settings for this website and set Auto-Play to Allow All Auto-Play. This allows automatic media playback on that website. Refresh Talkala only when no call is active, then check that it is ready to receive calls. This setting does not guarantee that a locked phone or background browser will ring.

What if Talkala opened inside another app? Some in-app browsers do not provide the microphone controls needed for calling. Use that app’s Open in browser option, or copy Talkala’s safe link into a regular browser. You may need to enter the number again. Talkala cannot choose or force-open another browser for you.

What if it still does not work? End the call before reloading or moving to another device. For problems after locking your phone or switching apps, read More about mobile calling. If you need support, include the call from History, the device and browser you used, and which direction of sound was missing.

Once the call is connected, select Keypad to show the phone-menu buttons. You can leave the keypad open for as long as you need, or select Keypad again to hide it. The call continues either way. Press the digits the other side asks for, such as 2 for English, an extension, an account ID, \*, or #.

Before starting a call, the keypad enters the destination number. While the outgoing call connects or rings, Talkala shows the call status and keeps the in-call keypad unavailable. Talkala does not send phone-menu tones while the call is still connecting or ringing.

What does a connection warning mean? Talkala has noticed a problem with the call connection. Your internet connection, browser or the calling service could be involved. The warning alone cannot tell us which one caused it.

What should I do first? Keep Talkala open. If you see Reconnecting, give it a moment to reconnect the same call. Avoid reloading the page or starting another call while it is trying.

What if I see Checking call or Check call audio? Ask the other person if they can hear you, and check that you can hear them. These messages mean Talkala is still checking the call or cannot confirm that the sound is working. Use Check again to check the existing call without restarting it. A timer that keeps running does not prove that you can hear each other.

What if the sound does not return? Select End call and wait for Talkala to confirm it has ended. Then check your connection and try again. Try again starts a new call only when you select it. Talkala never redials automatically.

What if the page reloaded? Reopening Talkala does not bring back the old audio connection. If the original calling tab or device is still open, return to it. Otherwise, end the call shown in Talkala before starting another. A restored incoming call may say Browser audio is unavailable; this page can end that call but cannot use its microphone or keypad.

Why did the call end? When the reason is available, Talkala may show that the line was busy, no one answered, the connection failed, or the call reached its time limit. A time-limit message is different from a connection problem. Sometimes there is not enough information to identify the cause.

Will the warning change my charge? No. The warning itself does not change the price. Calls that never connect are not charged. Connected calls follow the normal billing rules. Check History for the final duration and charge.

Where can I get more help? For screen locking or switching apps, read More about mobile calling below. For permission or headset problems, choose Microphone and audio help. If the problem continues, open the call in History and choose Get help with this call. The support form includes the call reference. Describe what happened and send it when ready. For a Team call, open its details in Team Activity.

Why can locking my phone or switching apps interrupt a call? Phones can pause browser pages to save power or free up memory. That can also pause the sound in a Talkala call. It may happen when you lock your screen, switch tabs or open another app. Your phone can sometimes pause a page automatically too.

What can I do during a call? Keep Talkala visible where possible. If you return after an interruption, ask whether the other person can hear you and check that you can hear them. A moving timer or a working internet connection does not prove the sound has returned.

Can Talkala stop the screen from locking? On supported browsers, Talkala asks the screen to stay awake during the call. Your phone or browser can refuse or stop this protection. You can consider extending your phone’s automatic screen-lock time for the call. This protection cannot prevent manual locking or guarantee that a call will keep working in another app.

What about Low Power Mode or Battery Saver? Power-saving settings may affect how your phone handles browser pages. If Talkala cannot keep the screen awake, that does not tell us whether a power-saving setting caused it. Keep the page visible and check the sound if you change settings or return to the call.

What if the sound stops? Return to Talkala. If it says Reconnecting, give it a moment. Check your volume and whether sound is going to headphones or Bluetooth. Use Enable sound or Check microphone if Talkala offers it. If you still cannot hear each other, select End call, wait for confirmation, then try again.

What if I change networks or receive a normal phone call? Moving between Wi-Fi and mobile data, or answering a cellular call, can interrupt Talkala. When you return, check both directions of the sound. Talkala cannot guarantee that a browser call will survive these interruptions.

Would a computer work better? If calls keep getting interrupted on your phone, a desktop browser is worth trying, especially for longer calls. Computers are generally less affected by the pauses phones use to save power. Keep the calling tab open and use a stable connection. End the current call before starting another on the computer; the sound does not transfer automatically.

Can I receive calls while my phone is locked? Do not rely on a mobile browser to ring or keep receiving calls while the screen is locked or another app is open. Keep Talkala open and visible when you are waiting for a call. Adding Talkala to your home screen is a shortcut; it does not add background calling or offline calls.

Can I close the reminder? Yes. The close button hides the advice without changing the call. Talkala remembers your choice in this browser where possible. More about mobile calling opens this Help Center guide in a new tab. You can also find it in the Help Center whenever you need it.

Talkala uses your available balance and the final per-minute rate shown in Phone to set a call limit. Example only: at $0.10 per minute, $1.00 can cover up to 10 minutes. Other call limits can make it shorter. Without more confirmed credit in time, the call ends at its current limit.

For personal calls that support refills while connected, adding credit manually or through Smart Auto Top-up can let Talkala reserve more time and extend the same call. The smallest manual top-up is $5. Opening checkout is not enough: the payment must complete and the credit must reach your available balance before the current call limit. See when purchased credit becomes available and how Smart Auto Top-up works.

If payment arrives too late, the automatic charge fails, another call limit is reached, or the connection ends, that call cannot continue. Credit posted afterward remains available for a later call. See how call billing works for the difference between a temporary hold and the final charge.

You can open Dashboard, Wallet, History, Contacts, or another signed-in Talkala page while the same call continues. A compact active-call banner lets you return to the call or end it.

Refreshing the browser, closing the tab, signing out, leaving the signed-in app, or opening another website can end or disconnect the browser call. Talkala warns you before those actions when it can.

If you choose to leave, Talkala tries to end the call before opening the next page. If you stay, the call keeps going.

Switching focus to another browser tab or application does not intentionally end the call. Keep the original calling tab open. Browser suspension, locking a mobile screen, closing the process, or losing the connection can still interrupt audio.

If a tab says it is not connected to an active call, return to the tab or device where you started the call to use audio or the keypad. The other tab can show the active destination and end the call, but it cannot take over the microphone or send keypad tones. When the call ends, the normal dialer returns.

Incoming calls use the full controls on their Phone page and floating controls elsewhere. If sound is blocked, Enable ringtone or Enable sound retries playback in that browser.

Before a call starts, Talkala checks the destination, full number, selected caller ID, and current Talkala rate for that attempt.

A carrier or number prefix can route differently from the country rate. If Talkala cannot confirm the route safely, it pauses the call before dialing.

If you use a caller ID from another supported country, Talkala needs a published rate for that caller ID country too. It does not silently reuse another country's price.

The dialer shows "Estimated rate" for the country preview, then "Final rate" once the full-number check succeeds. The signed-in rates page calls this "Final rate for this number." The per-minute rate stays locked during your call.

If the rate changes during the final pre-call check, Talkala updates the visible rate and asks you to press call again instead of connecting at a higher unseen price.

Talkala also blocks premium-rate, shared-cost, pager, and voicemail number types for price review instead of asking you to accept a higher charge.

This does not mean your number is invalid. It means Talkala needs to review the price before offering that call safely.

Some number types do not behave like ordinary landline or mobile destinations. Premium-rate and shared-cost numbers can be priced differently by carriers, and pager or voicemail destinations are not normal person-to-person call targets today.

When phone-number data identifies one of those types, Talkala blocks the call before dialing instead of asking you to accept the higher landline or mobile rate.

This is a pricing safety rule. It avoids starting a call where Talkala has not published a specific safe price for that number type.

Toll-free service numbers are different. Clear toll-free numbers, such as US 800 numbers, use the non-mobile landline pricing path unless a future service-number price category is added.

In many countries, calling a mobile costs more than calling a landline. Talkala first checks phone-number data to see whether the number is clearly fixed-line or mobile.

Toll-free service numbers, such as US 800 numbers, are treated as non-mobile service numbers for this pricing check. They should not trigger the mobile-versus-landline warning just because they are toll-free.

Some ordinary hard-to-classify number types, including numbers that may be fixed-line or mobile, unknown, internet-based, personal, or universal access numbers, can still continue when Talkala has not confirmed landline or mobile.

If the number type is still unclear and landline/mobile rates differ, Talkala uses the higher active rate instead of showing you a price that might be too low.

When that higher rate is used, the dialer shows "Final rate" before the call starts so you know which rate and minimum balance apply to that attempt.

Price benchmark page compares Talkala against published carrier rates from a checked research set. It shows that the savings claims are grounded in source-linked comparisons. It does not promise the same savings for every destination, carrier, or number type.

The live rate directory shows starting country rates. A carrier or number prefix can route differently. Enter the full number while signed in to see "Final rate for this number." If Talkala cannot confidently detect the number type before dialing, it uses the higher active rate instead of showing a price that might be too low.

Most personal paid calls need at least three minutes' cost in your available balance to start. This is a start check, not a three-minute charge. Example only: at $0.10 per minute, you need at least $0.30 available before dialing.

Personal calls that support adding credit while connected start by setting aside three minutes' cost. Before that time runs out, Talkala can set aside up to three more minutes from your available balance. It repeats this as needed, within the call's limits. You do not need to top up each time if you already have enough credit. If another full minute cannot be funded, the call ends at its existing time limit.

Reserved credit is set aside, not yet charged. For personal calls with funded extensions, it covers time already used and a little time ahead. Outgoing Team calls reserve their full allowed duration; see how Team credit works. Your available balance excludes that reserve, so it can fall in small steps during a long call. Any unused reserve returns after the final charge is confirmed.

While credit is reserved, the small balance display and the large balance card on the Phone page show the reserved amount separately from your available balance. That line disappears once no credit is held.

Example only: with a $10.00 balance and a $0.10 per-minute rate, the starting reserve is $0.30 and the available balance is $9.70. If you talk for 3 minutes and 56 seconds, the final charge is $0.40, because billing rounds up to four minutes. After unused reserved credit is returned, your balance is $9.60. A call that never connects costs $0.

Use the "Final rate" shown in Phone after your full number is checked. Public starting rates and the browser timer do not determine the final charge. For eligible personal calls, confirmed new credit can extend the same connected call within its limits. See why a call can end early.

This is a limited first-call offer, not an open-ended free trial. It only works if your available balance is zero, you have never completed a paid wallet top-up, you have not already used the offer, and the rate for the call you are placing is $0.99/min or less.

The destination must have at least one published landline or mobile price at or below $0.99/min in the rates that apply to your account. Landline and mobile prices can differ. Your call uses the price for the line type you dial.

Talkala may limit this first-call offer when account signals need review. If that happens, you can still add credit and call normally unless the account is separately blocked.

If the call connects, Talkala records the normal first-minute charge in your wallet history, then adds a matching promo credit so you pay $0. Because billing rounds up to the next full minute, even a short connected call uses the whole offer. If the call never connects, the offer stays unused.

If the call failed or went unanswered before it connected, Talkala releases the full temporary hold and does not create a final charge. If it connected before dropping or having poor quality, the charge follows the calling network's final connected status and duration.

Talkala does not offer self-serve refunds or an automatic quality guarantee for every failed, short, or poor-quality call. If a charge does not match what you expected, contact support with the timing and destination details. Where the records confirm a service issue or incorrect charge, Talkala may return the affected credit or add make-up credit.

Opening checkout or pressing Pay does not add credit by itself. Talkala adds it when the successful payment confirmation arrives.

If a payment is still processing, personal and Team credit stays unavailable until Stripe confirms success. A new Team is created after its initial credit payment succeeds.

After a personal top-up, Payment received. Adding credit… means the payment is confirmed and Talkala is waiting for the credit to appear. Wallet checks automatically for a short time and confirms the amount once it is recorded.

If the status is unavailable or still pending, use Check payment status or Get help before making another payment. Checking the status does not charge you. If Wallet cannot refresh, it keeps your entered amount and warns that the displayed balance may be out of date.

Where tax applies, Stripe calculates it during checkout and adds it on top of the wallet credit amount. The amount you select is the wallet credit face value; tax is not added as wallet balance.

Payment history dates use Coordinated Universal Time (UTC), so a payment made late in your evening may appear under the next calendar day in the app.

When a manual top-up succeeds, Talkala creates an in-app notification and can email you the top-up confirmation if Wallet email alerts are enabled in Settings.

For team wallets, top-up and Team Auto Top-up email alerts go to the team owner.

The restriction applies to the wallet that received the disputed payment. A Team payment affects the Team Wallet, even when a member used the same card for personal top-ups. Other wallets stay available.

Talkala restores the affected wallet automatically after Stripe reports that every open dispute for it was won. A lost or still-open dispute keeps the restriction in place. Contact support if you believe the payment or restriction is attached to the wrong account.

Choose `I need an invoice` before starting checkout. Stripe then collects the billing address and supported business tax ID details during checkout. Talkala does not collect or store those tax details in its own form.

The invoice is created only after the payment succeeds. Once it is available, you can find it in Billing under Payment history and in Wallet activity by opening that top-up row.

If Wallet email alerts are enabled, Talkala's top-up email also includes the invoice or receipt link when Stripe provided one.

For team wallet top-ups, those receipt or invoice links are included in the team owner's email alert when Stripe provides them.

If you do not ask for an invoice, Billing and Wallet fall back to the Stripe receipt when one is available.

A wallet promo code lowers what Stripe charges you at checkout. It does not lower the amount of calling credit you selected.

For example, if you choose a $50 top-up and use a 20% off promo code, Stripe charges $40 and Talkala adds $50 of paid wallet credit after the payment succeeds.

When Talkala can read the Stripe coupon math, the wallet screen shows an estimated payment before tax before you open Stripe Checkout. Stripe still calculates the final tax-inclusive total at checkout.

If the selected top-up qualifies for a Talkala bonus, the bonus is added separately on top of the selected top-up amount.

Promo codes can have limits such as expiration dates, redemption caps, minimum amounts, or first-time-customer rules. Stripe checks those rules during checkout.

If you turn it on while your balance is already below the threshold, it waits for the next qualifying balance drop.

Balance drops that count include final charges for calls you make, answered calls to your personal Talkala number when receiving is set up, and accepted SMS on a Talkala number. The saved card is charged only after the wallet balance crosses from at or above the threshold to below it.

After a call ends or an SMS charge is recorded, an automatic refill and its email may arrive later than that charge. Check that the refill has reached your available balance before starting another call that needs it.

After an answered incoming call, Talkala saves any triggered refill for retry if a connection fails. If the refill stays pending, contact support so its payment status can be checked before another charge is attempted.

For personal calls that support refills while connected, Smart Auto Top-up can try to add credit during an outgoing or answered incoming call. The call can still end at its prepaid limit if the payment or call extension does not finish in time.

Successful and failed Smart Auto Top-up attempts create in-app notifications and can also be emailed when Wallet email alerts are enabled.

If your saved card requires extra bank approval, the automatic charge fails instead of waiting for approval in the background. Check the alert, update your card if needed, or add credit manually.

For Team Auto Top-up, success and failure emails go to the team owner.

Smart Auto Top-up uses the same bonus tiers as manual top-ups. A qualifying automatic refill creates the paid auto top-up credit plus a separate bonus-credit entry after Stripe confirms the payment.

When Stripe reports that a wallet payment is disputed or reversed, Talkala stops new calls, number purchases, automatic top-ups, and new caller-ID verification for the personal account or team connected to that payment.

The restriction does not delete the account. You can still sign in and view history, contacts, wallet records, billing records, and support.

A disputed Team payment affects the Team Wallet. A member's personal wallet stays available unless it has its own disputed payment. Spending resumes when every dispute linked to that wallet has been won. A lost or open dispute keeps the restriction in place. Contact support if the payment status or affected wallet looks wrong.

Remaining unused paid balance from a wallet top-up can be refunded within 14 days of purchase. Credit already used for successfully completed calls is not refundable.

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

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

When support corrects a wallet balance, the correction appears as its own wallet-history entry. Support credits and balance corrections do not rewrite or hide the original payment or usage record.

A maintenance pause applies to all outgoing Team calls, even if the call button is still available in an open tab. Adding credit or changing your caller ID does not remove the pause.

Calls already admitted can finish and settle under the normal billing rules. Unused reserved credit returns after settlement. The outgoing pause does not itself disable personal calls or incoming Team calls; their usual availability rules still apply.

Calls can show the destination, recorded connection and end times, duration, outcome, rate, and final recorded charge. Historical details appear only when Talkala has a record of them.

Open View billing events to see the call's reservations, releases, charges, and refunds in time order. A reservation temporarily holds balance; it is not an extra charge. The list is independent of the activity page's date filter. Long histories show only the latest 100 events and say when earlier events are omitted.

Top-ups show their source and a receipt or invoice link when available. Received SMS details show the sender, receiving team number, message segments, and rate.

Owners and admins can review team activity. Caller-role members can review only their own permitted activity; expanding a row does not grant access to other members' calls.

When you are inside a team, you can also tap its name and arrow near the top of the screen to switch teams. Long team lists scroll inside the selector.

On the Phone screen, the round history-and-star button opens Recent calls. Switch to Favorites inside the same panel. Choosing a destination fills the dialer; it does not start a call.

Open your team's Settings and find Team image under Workspace details. Choose one of the illustrated avatars or upload your own. Other members can see the image but cannot change it. Removing an uploaded photo restores the originally assigned avatar on new teams. Older teams without one show initials.

Talkala assigns a new team one of twelve avatars when payment confirms creation. It avoids avatars already assigned to your active teams until all twelve have been used; then they can repeat. You can choose any avatar yourself, even one used by another team.

To upload, choose a PNG, JPEG or WebP image up to 6 MB and 24 megapixels, with no side over 8,192 pixels. Drag and zoom to fill the square. Talkala saves only a small square version.

You can choose an avatar or image before checkout. This optional choice stays in the same browser tab for up to 24 hours and is saved after team creation. If it cannot be saved, payment and team creation still succeed; change it in Team Settings. A later image change is not overwritten when returning from checkout.

A team starts when the first team credit Checkout succeeds. The buyer becomes the team owner, and Talkala adds the purchased credit to the team balance.

If another paid checkout reaches Talkala after a team with the same name has already been created for that owner, Talkala does not create a duplicate team. It starts a refund for the second charge and keeps the case under review until Stripe confirms it. The same applies when a checkout is paid after the owner's account closes.

Team credit has its own bonus tiers: no bonus below $400, 5% at $400 or more, 10% at $1,000 or more, and 12% at $2,500 or more. The same ladder applies to qualifying Team Auto Top-up refill amounts. Promo codes are for manual Checkout only and discount the Stripe payment, not the selected team credit face value.

Team calls use the team balance when you place them from the team phone screen. Personal wallet credit, personal Smart Auto Top-up, and the personal free first minute do not apply to team calls.

Before an outgoing Team call starts, Talkala reserves enough shared credit for its allowed call length, within your remaining monthly limit. That can temporarily reserve most of the team balance, so another member may need to wait or the team may need more credit. After the call ends, Talkala charges the actual billable time and returns the unused reserve. Incoming Team calls reserve credit in shorter windows as described below.

When you call from a team, the caller ID menu is scoped to public caller ID, team-owned voice-capable numbers, and external caller IDs verified for that team. Personal numbers and personal verified caller IDs stay in your personal workspace.

Owners and admins can set optional monthly calling limits for members. Talkala checks a member's current-month team call charges and active holds before allowing another team call to start. A full Team Wallet cannot override a member's remaining limit; see how Team incoming calls use credit for a dollar example where receiving is available.

The person who starts the team becomes its owner. The owner can change admin and caller roles, transfer ownership to an active administrator after confirming their identity, close the team, and use every team-management area.

Admins can manage team credit, members, numbers, contacts, and settings where the product allows it. Callers can place team calls and use shared contacts, but they cannot manage the team or its billing.

Team Messages is receive-only and available only to owners and admins. Caller-role members can call Team Contacts but do not see a message action.

Owners and admins can invite an email address. Talkala sends the invite by transactional email when email delivery is configured, and the invited person must sign in with that same email address before Talkala activates the membership.

Owners and admins buy and manage team-owned numbers from Team Numbers. The current finder covers available U.S. and Canada numbers. After Stripe confirms the monthly payment, Talkala adds the number to the selected team instead of the buyer's personal number list.

Owners and admins can rename a team number, schedule cancellation for its paid-through date, release it immediately with an irreversible warning, and choose one default. The default is the team's preferred owned caller ID and the inbox that opens first in Team Messages.

The default team number is a Team Messages and caller ID preference, not a routing rule. Texts still arrive in the inbox for the team number that received them. When you open Team Messages, Talkala shows the default team number inbox first when it is available.

Received SMS is saved to the team and charged from Team Credit. If Team Auto Top-up is ready, a received-SMS charge can trigger a refill from the saved team card.

When Receive Team calls appears for an eligible paid U.S. or Canada voice number, an owner or admin can turn it on in Team Numbers and choose up to ten active teammates in Team Settings. The option may appear gradually. If setup fails, calls stay off until an owner or admin retries it. Turning receiving off or starting number cancellation stops new calls to that number; calls already accepted can finish and settle.

Assigned teammates must keep Talkala open in a supported browser, prepare the microphone, and set themselves Available. Everyone who is ready rings together; the first approved answer takes the call. Dismiss for me stops the ring only for that teammate. Team and personal calls still share one active-call limit per user.

An answered Team incoming call reserves up to five affordable whole minutes from the Team Wallet and the answering member's remaining monthly limit. Connected time costs 3¢ per started minute for a U.S. or Canada local number, or 5¢ for a toll-free number. Talkala does not charge the Team Wallet for ringing, missed calls, or failed connections; unused credit returns after final settlement. The phone provider may still charge Talkala for waiting time.

Example only, where Receive Team calls is available and set up: on a 3¢ per-minute local number, a Team Wallet with $1.00 and a member with 9¢ left under their monthly limit can reserve three minutes (9¢), not five. If the member has only 3¢ left, one minute can start. Talkala tries to reserve more affordable time before the current limit; the call ends at that limit if either the Team Wallet or the member's allowance cannot cover another whole minute.

Team Contacts are shared inside one team. Active members can search and use them from Team Contacts or Team Phone.

Owners and admins can add, edit, favorite, delete, import, export, or copy personal contacts into the shared list. Caller-role members can use the contacts but cannot change them.

Team contact notes are visible to members who can access that team. Personal contacts stay personal unless an owner or admin explicitly copies them into Team Contacts.

Team Auto Top-up can refill Team Credit from a saved card after a qualifying balance drop. Only the team owner can manage the threshold, refill amount, and pause or resume setting from Team Wallet. If the team has no saved card, the next manual Team Credit checkout can save one.

If Team Auto Top-up has already started when ownership changes, that refill keeps its original payer, saved card and amount. Once payment confirms, the credit goes to the same Team Wallet, and the current owner receives the Team payment notification.

Owners and admins can set a monthly calling limit for individual members. An admin cannot change the owner's member settings. Talkala checks the member's finalized team call charges and active call reserves for the current month before another team call starts.

Member limits apply only to team calls. They do not change the member's personal Talkala balance or personal calls. A Team Auto Top-up adds spendable Team Credit only after payment confirms; it does not raise anyone's monthly limit.

Open My Numbers and use Buy a Number to choose a country, search available numbers, and review the monthly fee before completing checkout.

Open the number's details to turn on Receive calls and check that Receive SMS is on. Keep Talkala open and online to answer calls in your browser.

You can have multiple Talkala numbers, each with its own monthly fee. Add labels to recognize them and use Calling from on Phone to choose your outgoing number. Calls and received SMS use wallet balance separately from number rental.

Your balance covers calls you make, received SMS, and answered calls to your Talkala number. The number itself is a separate monthly rental that keeps it assigned to you.

Talkala numbers can receive SMS in the browser while Receive SMS is on for that number. Each SMS Talkala accepts still costs wallet balance. US Talkala numbers cost $0.02/SMS, and Canada Talkala numbers cost $0.03/SMS. Prices are shown per SMS for readability, but wallet billing is per SMS segment. A short plain-text SMS is usually one segment. Longer texts, or texts with some special characters, can count as multiple segments.

These charges are separate. Wallet balance does not pay the monthly number rental, and an active number rental does not include free received text messages or free incoming-call minutes.

When receiving calls is set up for your personal number and Receive calls is on, only answered connected time can use wallet balance. The price is based on your Talkala number, not where the outside caller is calling from. US and Canada local Talkala numbers are $0.02/min when answered; US and Canada toll-free Talkala numbers are $0.04/min when answered.

Missed, declined, busy, unavailable, unanswered, and low-balance calls do not cost you anything from Talkala. The outside caller may still pay their own phone company separately for the call.

Where tax applies, Stripe calculates it during number checkout and adds it on top of the displayed monthly base price.

Only plain-text received SMS is charged. MMS with photos, videos, audio, contact cards, or other media is not supported and does not create a wallet charge or inbox message.

Number activation, renewal, scheduled cancellation, and monthly payment failure can also be emailed when Numbers email alerts are enabled in Settings.

A selected number can occasionally become unavailable between checkout and final provider activation. If Talkala cannot safely finish activation, it cancels the subscription so it will not renew and refunds the verified charge tied to that checkout.

The refund can take time to move from processing to completed at Stripe and your bank. Talkala keeps the failed activation under review until the refund succeeds and any temporary provider resource has been cleaned up.

No number is added to your account when activation fails. Contact support if the refund remains pending or your bank does not show it after its normal processing time.

When someone calls your Talkala number, it can ring right in your browser. You need a Talkala number first because that is the number people call back. You answer from Talkala, not your personal phone, so your personal number can stay private.

Use the Receive calls switch to choose whether calls to that number should ring in Talkala. Some numbers may need setup before they can receive calls, and newly rented numbers still start with Receive calls off.

Talkala needs to be open in your browser to ring. If you are signed out, offline, or the tab is closed, Talkala cannot ring here yet. Answering may ask for microphone access if your browser has not already allowed it.

Your available balance must cover at least three minutes at your number's incoming rate before you can answer. At $0.02 per minute, that means at least $0.06 available. This is a starting check, not a three-minute charge.

When you answer, Talkala sets aside a temporary hold. Personal calls that support adding credit while connected start with three minutes' cost reserved, then can reserve up to three more minutes at a time as needed and affordable. This is not the final charge. Any unused amount returns after final billing. See how call billing works.

You only pay Talkala when an incoming call actually connects. Missed, declined, busy, unavailable, unanswered, and low-balance calls do not cost you anything from Talkala. The person calling you may still pay their own carrier separately.

Choose normal cancellation when you want the monthly rental to stop renewing. Talkala keeps the number active until the paid-through date shown in the app, then releases it and removes it from your account.

Choose immediate release only when you are finished with the number now. It cannot be undone, the number may not be recoverable, and already-paid subscription time may not be refundable.

Use My Numbers to buy a Talkala number, add or retry external caller-ID verification, rename numbers or caller IDs, remove external caller IDs, set SMS or caller-ID defaults, and clear the default caller ID.

Your SMS default is a Messages preference, not a routing rule. Texts still arrive in the inbox for the Talkala number that received them. When you open Messages, Talkala shows your SMS default inbox first when it is available; you can switch to another owned-number inbox anytime.

Settings > Calling Identity is summary-only. It shows your current SMS default, caller-ID default, inventory counts, and a Manage my numbers link. You can also clear the default caller ID there without deleting the caller ID.

The Dialer caller-ID picker can open My Numbers when you need a number or want to add a custom caller ID.

Team-owned numbers and team-specific verified caller IDs are managed from Team Numbers and Team Settings, not from personal My Numbers.

Caller ID matters because people are more likely to answer a number they recognize.

Verified caller IDs can have labels in My Numbers. If you skip the label, Talkala shows the full phone number, and you can add or change the label later.

You can remove an external verified caller ID from My Numbers. Talkala removes the outside verification before it deletes the caller ID from your account. If that cleanup is temporarily unavailable, the caller ID stays visible so you can retry safely.

You can clear a verified caller ID as your default caller ID from My Numbers or Settings > Calling Identity without deleting it, or change the default by choosing Set caller ID on another number.

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

Add or retry external caller-ID verification from My Numbers. Open the verified caller IDs section, choose Add caller ID, and complete the validation call when prompted.

Before a new validation call can start, your email must be verified and the applicable personal or team wallet must have completed a paid top-up. Accounts blocked or held for a high-risk review cannot start this call; contact support if you believe that restriction is a mistake.

Talkala limits verification attempts by account, phone number, and request source. One owner can have at most three active verification requests, and an unfinished request expires after two hours. If you are asked to wait, deleting and adding the caller ID again will not reset that waiting period.

The add or retry action may be temporarily hidden while Talkala or its calling provider pauses new caller-ID validations. Caller IDs that are already verified remain in My Numbers.

This is more than a local form. The verification step has to complete successfully outside Talkala, so it can fail or get temporarily limited for reasons Talkala does not control.

If the calling network already recognizes the number as verified, Talkala can mark the caller ID ready instead of asking for another verification call.

When a caller ID becomes verified, Talkala sends a Calls notification and an email if Calls email alerts are turned on. If verification fails after you leave the page, Talkala sends the same kind of alert so you know to retry from My Numbers.

Starting a verification call does not send a notification or email by itself.

One common stumbling block: if you already have a Talkala number, use it as a Talkala caller ID. Do not try to add it again as an external caller ID.

Talkala preserves the text it receives from the messaging provider, including spaces and line breaks. It does not guess replacements for damaged characters.

If a message contains unusual control characters or a replacement symbol, the inbox says that some characters may not have arrived correctly. This is a warning about possible text damage, not proof of which phone, carrier or provider caused it. Ordinary brackets, Spanish accents and emoji do not trigger the warning.

If the text matters, confirm it with the sender through another channel. Contact support with the message time and receiving Talkala number. Avoid sharing passwords, verification codes or other sensitive message contents.

A visible character is not always one SMS encoding unit. Brackets and euro signs use extra units in GSM-7, while emoji and some accents require Unicode encoding. Long messages can therefore have several billable parts. Talkala uses the provider's valid part count when supplied and otherwise estimates from the received text.

A text warning does not create an extra charge or automatically resend the message. The usual per-segment price still applies to an accepted SMS.

The Messages page is a receive-only inbox, not a full texting tool. Texts sent to your Talkala number can appear there, but you cannot send texts from the browser.

While Messages is visible, the inbox checks for new texts about every 20 seconds. It also checks when you return to the tab. You can keep reading an older conversation while new texts arrive.

If Messages cannot load your inbox, it shows a loading error and tries again while the tab is visible. You can also use Retry without reloading the page. When switching numbers, conversations from the previous inbox are cleared while the selected inbox loads. A loading error alone does not mean you have no number or that incoming texts have stopped.

The inbox supports 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. You rent the Talkala number monthly, and each received SMS uses prepaid wallet balance before Talkala accepts it.

US Talkala numbers cost $0.02/SMS, and Canada Talkala numbers cost $0.03/SMS. Other number countries can differ, and the Messages page shows the active SMS amount when Talkala knows it for your assigned number.

Wallet billing is per SMS segment. A short plain-text SMS is usually one segment. Longer texts, or texts with some special characters, can arrive as multiple segments and cost more than one SMS.

Delivery is strict. New texts are dropped if the number rental is inactive, the wallet cannot cover the next segment, or Talkala does not have an SMS price for that number.

Texts with media are also dropped because the inbox supports text-only SMS.

When an accepted SMS leaves your wallet below the next-segment minimum, Talkala creates a low-balance notification.

Talkala can also email that warning if Wallet email alerts are enabled.

For team-owned numbers, low-balance and dropped-message email alerts go to the team owner.

If more texts arrive while the same low-balance warning is active, Talkala records the drops without sending a fresh email for every single text.

The SMS inbox can only show messages for Talkala numbers assigned to your account. If you do not have a Talkala number that can receive texts, you do not get an SMS inbox.

If you rent more than one Talkala number that can receive texts, Messages separates inboxes by the Talkala number that received the text. The same person texting two different Talkala numbers appears as two separate threads.

Your SMS default is a Messages preference, not a routing rule. Texts still arrive in the inbox for the Talkala number that received them. When you open Messages, Talkala shows your SMS default inbox first when it is available; you can switch to another owned-number inbox anytime.

You can label Talkala numbers, for example Personal, Company Support, or General. Those labels help you recognize each inbox in Messages and on the My Numbers page.

Older SMS threads that do not have a stored receiving number can appear in a Legacy inbox. New SMS goes to the exact number inbox that received it.

The inbox is receive-only. You can see texts tied to your number, but you cannot send general texts from your browser.

Opening a thread marks its unread badge as read after the latest messages load.

When a thread is not linked to a saved contact, the thread header offers Save to contacts. That opens Contacts with the new-contact form and the thread phone number prefilled so you can save them without copying the number.

Every accepted SMS also creates an in-app notification that links back to the receiving inbox. Talkala does not email you for every received text.

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

Talkala does not publish a detailed country-by-country SMS coverage list the way it publishes voice rates. Treat SMS as a smaller part of the product.

The inbox only accepts messages that fit the prepaid and text-only rules.

An SMS sent from another country may fail before it reaches Talkala, even when your number and wallet are ready. Talkala cannot show a text it never receives. Ask the sender to check with their carrier, or contact support with the send time and receiving Talkala number. Do not share the message contents if they are sensitive.

If the number rental is inactive, SMS pricing is not configured, or the wallet cannot afford the next SMS segment, the message does not appear in your inbox.

Messages with media also do not appear because the inbox is text-only.

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

This is why a number can look set up but still miss new texts until the billing or configuration issue is fixed.

Talkala can email low-balance and first dropped-message alerts when Wallet email alerts are enabled.

Repeated drops during the same low-balance state do not each get a separate email. The missing text itself is not stored for later delivery.

Talkala can also quietly drop a burst of repeated or distributed incoming texts to protect one attacked number. An abuse-dropped text is not stored, does not change its thread, does not use wallet credit, and does not trigger a separate alert for every attempt. Calling remains available.

The phone network may still charge Talkala for delivering an incoming SMS to its webhook even when Talkala drops that message locally.

If you already have a call in progress, Talkala blocks a second call. Finish or end the first call, then try again.

Calling from the browser cannot guarantee the connection, location accuracy, or emergency-service connection that emergency-capable phones provide. If you need emergency services, use a mobile phone or landline.