Before your team can dial a single prospect, Calling has to be turned on for your organization, someone needs a Wyra phone number, and (optionally) you can plug in a phone-lookup provider you already pay for. This guide covers that setup lifecycle end to end — request access, get numbers, find a number for a specific lead, and see where the results land afterward.
Calling is approval-gated. It stays behind a "Request beta access" screen for your whole organization until the Wyra team reviews and approves your request — everything below only applies once that happens.
Looking for how to actually make a call?
This article is the setup guide — access, numbers, and configuration. For dialing, muting, the keypad, and what the prospect sees, see Wyra Calling →. Calling is human-led throughout: a person on your team places every call from the browser dialer — Wyra never dials or speaks on its own.
Requesting access
Anyone on your team can request beta access — it unlocks for the whole org.
Access is granted per organization, not per person — once approved, every teammate sees Calling unlocked. You can request it from a couple of places:
The Phone icon in the top navigation
Click it, then Unlock phone access. You'll land on a Wyra calling · Beta pitch page with a Request beta access button.
Settings → Calling
If your org hasn't been approved yet, this section shows the same unlock pitch in place of the usual Phone Numbers and Call Configurations tabs.
You can also request access straight from a lead: click the phone glyph on any row in Interactions before your org is approved, and a smaller "Calling is in beta" modal offers the same Request accessbutton. Either path submits the same request — there's no form to fill in beyond clicking the button, since your name and email come from your account automatically.
While you wait
A pending badge shows up everywhere calling would otherwise appear.
Once you've requested access, a small orange clock badge appears on the Phone icon in the nav — open it and it reads "Pending verification — we'll notify you when it's approved."The phone glyph on any Interactions row gets the same clock badge with a "Pending beta access verification" tooltip on hover. Dashboard → Callingshows a plainer lock icon instead — it stays locked the same way whether you haven't requested access yet or you're still waiting on approval. There's nothing further to do either way — the Wyra team reviews requests and approves them from their side.
You may need to reload once approved
Approval status doesn't poll live in the background. If your request was just approved, refresh the page (or navigate away and back) to see the pending badge clear and the Calling surfaces unlock.
Once approved — Settings → Calling
Phone Numbers — get a Wyra number for each AI SDR.
Settings → Calling has two tabs: Phone Numbers and Call Configurations. Phone Numbers is where each of your AI SDRs gets its own dedicated Wyra number to call from — a header reads something like "2 of 5 AISDR numbers used," capped at one number per AI SDR in your org. A table lists every number already assigned, with columns for Number, AISDR, and Status.
Click Get Wyra phone number to open a four-step drawer:
Intro
A quick pitch on what a Wyra number gets you — receive/place calls with automatic logging, numbers in the US and other supported countries, one dedicated number per AISDR.
Generate a number
Choose a Country, and for the US an optional Area code, then click Generate number. Pick from the results (Load more paginates), then Continue.
Assign to an AISDR
Choose which AI SDR the number will be purchased and attached to — only AI SDRs that don't already have a number appear in the list. Click Get this number.
Success
"{number} is ready" confirms the purchase and shows which AI SDR it's assigned to — that AI SDR can start calling immediately.
This is a different "number" than a lead's phone number
Phone Numbers provisions your AI SDR's own outbound Wyra number — the one prospects see as caller ID. It has nothing to do with finding a lead's personal phone number, which is a separate feature covered further down in this guide.
Settings → Calling
Call Configurations — one org-wide setting today.
The Call Configurations tab currently exposes a single toggle: Call recording. Turn it on and every outbound call is recorded by default for coaching and QA, for your whole organization — consent rules for recording still apply per region. This sets the org-wide default — reps can still switch Record this call on or off for an individual call from the dialer in the contact drawer. Recording is required for the AI call summary.
Finding a number for a lead
Wyra searches for a phone number automatically — the lookup waterfall.
Open a lead in Interactions and click into the call panel. If Wyra doesn't already have a number for that lead, it kicks off a waterfall search on its own — you'll see a live checklist of each source as it's tried: Wyra's own database first, then Wyra's own lookup at no cost to you. Only if Wyra finds nothing does it try the data providers you'veconnected — Lusha first (responds quickly), then Apollo (searches asynchronously and can take a few minutes, shown with its own "still working" state). Your provider credits are never spent on a number Wyra already has.
If nothing is found
A card tells you exactly what happened. With providers connected it names the sources searched — "No number found across Wyra, Apollo, and Lusha," for example — with Search again and Enter number manually. With none connected, it reads "Connect Apollo or Lusha to search your own sources," adding a Connect button next to Enter number manually.
Deeper search
Once a number exists, a "Search my connected sources" button re-runs the waterfall against your connected Apollo/Lusha accounts — a confirmation warns this spends provider credits before you confirm.
Every number found is listed with a source chip (Wyra, Apollo, or Lusha) so you always know where it came from. A few corrections are built in:
Flag a wrong number
Any provider-sourced number gets a flag icon — "Flag as wrong number." Flagged numbers move to a struck-through row rather than disappearing, with a "Mark as right" link to undo the flag without losing its history.
Add or edit a number yourself
"+ Add a number" lets you type one in by hand. Numbers you add this way are marked user-verified and get inline Edit/Delete icons instead of the flag action.
Do Not Call and identity flags
A number flagged Do Not Call shows a red badge and can't be selected to dial. A number where the provider matched a different name than the lead's shows a "⚠ Verify" badge — worth a second look before calling.
Edits made in the dialer are saved
If you edit the number directly in the dialer before calling, the button relabels to "Save & Call." Clicking it saves your correction to the lead's contact record and dials — the save never blocks or delays the call itself.
Connecting your own data provider
Settings → Integrations → Data Providers.
If your team already pays for a phone-lookup subscription, connect it so Wyra uses your account for number lookups alongside its own. Scroll past the CRM integration cards in Settings → Integrations to the Data Providers section — three tiles are listed:
Apollo
ConnectableClick the tile, paste your API key, and click Connect — Wyra validates the key before connecting it.
Lusha
ConnectableSame flow as Apollo: click the tile, paste your API key, Connect. Lusha responds synchronously during the lookup waterfall.
ZoomInfo
Coming soonListed in the catalog with a "Soon" badge — the tile is dimmed and not yet clickable. It isn't part of the lookup waterfall yet.
A connected tile shows a green dot and "Connected" — hover it to see who connected it and a masked version of the key. Click a connected tile to Update API key or Disconnect. If a key stops working, the tile turns amber and reads "Reconnect," with the last error available on hover.
The fastest way in is from a "not found" card
When a lookup for a specific lead comes up empty and you have no providers connected, the not-found card's Connect button deep-links you straight to this Data Providers section — no need to hunt for it in Settings first.
Where calls land afterward
Every call is logged automatically — outcomes, logs, and analytics.
After a connected call ends, a short panel asks "How was the call?" — pick a 1–5 star outcome with a couple of reason chips and an optional note, or skip it. Unanswered, busy, failed, and voicemail calls don't ask for an outcome, and some reasons ask for a follow-up date. For some calls Wyra proposes a rating on your behalf from the call transcript; it's labeled "Rated by [AI SDR name] from the call" with a Correct rating link so you can always override it — the call itself is still placed entirely by a person, this is just Wyra reading the transcript afterward.
Call logs
Click the Phone icon in the nav for a Recent dials list, or View all calls for the full Call logs dialog — filterable by AI SDR, up to your most recent 50 calls.
Back in Interactions
The latest call's result — answered, no answer, busy, voicemail, and so on — shows up as a colored phone icon on that lead's row in Interactions, so the rest of your team can see how a call went without opening it.
For the full picture across every AI SDR — dials, connect rate, talk time, and a call-outcomes breakdown — check Dashboard → Calling.
Dashboard — Summary & Calling →Where to go next