> ## Documentation Index
> Fetch the complete documentation index at: https://help.pipelime.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Get a phone number for a lead

> The Get Phone button, what it costs, when you are charged and the three answers it can come back with.

export const UiPath = ({children}) => {
  const parts = String(children).split(/\s*(?:→|>)\s*/).filter(Boolean);
  return <span className="pl-path">
      {parts.map((part, index) => <span key={`${index}-${part}`}>
          {index > 0 && <span className="pl-path__sep">→</span>}
          {part}
        </span>)}
    </span>;
};

export const Screenshot = ({id, alt, caption, frame = 'browser', url, marks = [], lang = 'en', workspace = 'northwind-outbound'}) => {
  const src = `/images/screenshots/${lang}/${id}.png`;
  const chrome = url ? `app.pipelime.ai/${workspace}${url}` : 'app.pipelime.ai';
  return <figure className={`pl-shot pl-shot--${frame} not-prose`}>
      <div className="pl-shot__frame">
        {frame !== 'bare' && <div className="pl-shot__bar">
            <span className="pl-shot__dots">
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
            </span>
            <span className="pl-shot__url">{chrome}</span>
          </div>}
        <div className="pl-shot__media">
          <img src={src} alt={alt} loading="lazy" />
          {marks.map(mark => <span key={mark.n} className="pl-shot__mark" style={{
    left: `${mark.x}%`,
    top: `${mark.y}%`
  }} aria-hidden="true">
              {mark.n}
            </span>)}
        </div>
      </div>
      {caption && <figcaption className="pl-shot__caption">{caption}</figcaption>}
    </figure>;
};

By the end of this page you know what clicking **Get Phone** on a lead does, what it costs, and what each of its outcomes looks like.

<div className="pl-availability">
  <div className="pl-availability__row">
    <div className="pl-availability__label">Where</div>
    <div className="pl-availability__value"><span className="pl-path">Leads<span className="pl-path__sep">→</span>Prospects</span></div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">Your role needs</div>
    <div className="pl-availability__value">Read access to Prospects <code>read-leads</code>. Admin, Member and Viewer have it by default.</div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">To create or change</div>
    <div className="pl-availability__value"><code>create-leads</code> to add one, <code>update-leads</code> to change one, on top of the permission above.</div>
  </div>

  <div className="pl-availability__note">If you cannot find this in your sidebar, your workspace may have a custom menu configuration. Contact support and we will check it for you.</div>
</div>

## Before you begin

* You need the `update-leads` permission. Without it, neither **Get Phone** nor **+ Add Phone Number** renders on the lead at all.
* There have to be credits left. The allowance comes from the subscription the account owner holds, and what counts against it is every workspace that owner has, not only this one. With none left, the upgrade prompt opens instead of a search starting.
* There has to be something to search on: a LinkedIn URL on the lead, a matched profile from when the lead was found, or the website of the company the lead belongs to. The button still shows on a lead with none of these, but the search then comes back empty every time.

## Steps

<Steps>
  <Step title="Open the lead's Contact Information card">
    Open a lead from <UiPath>Leads → Prospects</UiPath>, or from wherever else you found it. In the left
    column, the **Contact Information** card holds **Phone Numbers** underneath **Emails**. **Get Phone** (1)
    sits next to **+ Add Phone Number**, whether or not the lead already has a number on file, with a small
    coin badge on it that always reads 5.

    <Screenshot id="leads/get-a-phone-number--button" url="/leads/prospects/142" alt="The Phone Numbers section of the Contact Information card, with an outlined Get Phone button carrying a coin badge reading 5, and a tooltip open beneath it reading '5 credits per phone number. Only charged if found.'" caption="The badge and the tooltip say the same thing two ways: the charge is per number, and only for one that our data provider actually hands back." marks={[{ n: 1, x: 78, y: 46 }]} />
  </Step>

  <Step title="Click Get Phone">
    The button switches to **Searching...** with a spinner and stops taking clicks. The request goes out to
    our data provider inside the click itself rather than as a queued background job, but the button stays in
    that state until the whole search is over, which can take a little under two minutes.
  </Step>

  <Step title="A number turns up">
    When our data provider hands one back, either right away or a little later, a notification with a tick
    reads "Phone number(s) found!" and the number lands in **Phone Numbers**, with a copy button and Call
    and WhatsApp shortcuts beside it. A number that carries a country code is shown behind that country's
    flag and grouped for reading. One stored without a country code is printed exactly as it arrived, with a
    phone icon where the flag would be, because a bare national number cannot be assigned a country without
    guessing.

    <Screenshot id="leads/get-a-phone-number--found" url="/leads/prospects/216" alt="The Phone Numbers section showing one revealed number behind a country flag, the grouped digits, and copy, Call and WhatsApp icons beside it" caption="Once a number is on the lead, it looks exactly like one you typed in yourself." />
  </Step>

  <Step title="Nothing turns up yet">
    Most numbers reach us after the request rather than in reply to it, so a first notification reads "Phone
    search initiated. Checking for results..." and the page then re-checks the lead up to eight times over a
    little under two minutes. If none of those checks finds a number, the last thing you see reads "Phone
    verification in progress. The number will appear automatically when ready." There is no separate message
    telling you the lead has no number, and the page stops re-checking at that point: a number that lands
    after it gave up is on the lead, but you have to reopen the lead to see it.

    <Screenshot id="leads/get-a-phone-number--not-found" url="/leads/prospects/142" alt="The Get Phone area with a notification reading 'Phone search initiated. Checking for results...' after clicking the button" caption="A representative example, captured against a simulated response: this page has no separate 'no number found' screen, only this searching notice, whichever way the search ends." />
  </Step>
</Steps>

## What happens next

<Check>
  A found number stays on the lead in **Phone Numbers**, ready to call or message on WhatsApp. Nothing new
  appears on the lead if the search comes up empty.
</Check>

A click ends one of three ways: a number is on the lead before the button stops spinning, one arrives while
the page is still re-checking and lands on the card on its own, or nothing arrives inside that window and the
lead is left as it was.

You're only charged for a number our data provider actually hands back, at 5 credits each, and never for a
search that finds nothing. If the provider has more than one number on file for a lead (a mobile line and a
work line, say), each new one it returns is charged, not just the first. A number already on the lead is not
charged for a second time. A click keeps the search open for 24 hours, so an answer that arrives well after
you've closed the tab can still add the number to the lead on its own, without you clicking **Get Phone**
again.

This is the same lookup a [lead source's phone toggle](/en/finding-leads/phone-enrichment-option) runs
automatically while it's finding leads, except that one charges for a single number per lead and spends it on
a mobile whenever the provider returns one. Clicking **Get Phone** by hand has no such ceiling.

## Troubleshooting

<AccordionGroup>
  <Accordion title="It just keeps searching and I never see a number">
    This page shows the same thing no matter why a search doesn't produce a number: the lead has nothing to
    search on, our data provider genuinely has no number for this person, or phone lookups are paused for
    every workspace at once. That last one happens when the provider starts refusing reveals account-wide,
    usually because its own mobile-number quota has run out, and the pause lasts up to six hours. Lead
    sourcing and email lookup keep working through it; only phone lookup stops. All three end the same way
    here, with the searching notice and then nothing, and you are not charged in any of them. Try again in a
    few hours; a pause of that kind clears on its own well before the day is out.
  </Accordion>

  <Accordion title="There's no Get Phone button on this lead">
    The button needs the `update-leads` permission, the same one **+ Add Phone Number** needs. Without it,
    both controls are removed rather than shown disabled, so there's nothing on screen to explain why they're
    missing.
  </Accordion>

  <Accordion title="The upgrade prompt opened instead of searching">
    The credit allowance behind this workspace is spent. The upgrade prompt opens on its own as soon as the
    click comes back. What the card itself reports is generic: "Error retrieving phone number", both as a red
    line under the button and as a notification, with no mention of credits either time. See
    [what consumes credits](/en/billing/what-consumes-credits) for the rest of what draws from the same
    balance.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Also find phone numbers automatically" icon="phone" href="/en/finding-leads/phone-enrichment-option">
    The same lookup, run for a whole lead source as it finds leads, charged for one number per lead.
  </Card>

  <Card title="What consumes credits" icon="coins" href="/en/billing/what-consumes-credits">
    Every other action in the product that draws from the same balance.
  </Card>

  <Card title="Connect a WhatsApp number" icon="message-circle" href="/en/channels/connect-whatsapp">
    What a revealed mobile number is usually for.
  </Card>

  <Card title="The lead details page" icon="id-card" href="/en/leads/lead-details-page">
    Every other card and header action on the same page this button lives on.
  </Card>
</CardGroup>
