Pular para o conteúdo
NovoVeja como
Melhoria

More reliable website import

We rebuilt the website crawler with automatic failover and smarter retries, so importing a site recovers from temporary hiccups and captures more pages.

Importing a website into a knowledge base sounds simple, but the open web is messy: pages time out, servers rate-limit, and a single transient error used to be enough to drop a page — or stall an import partway through. We've rebuilt how website import works so those moments recover on their own.

Built to recover

The crawler now runs with automatic failover. If the primary path to fetch a page has trouble, the work shifts to a backup path instead of failing, and transient errors are retried with sensible backoff rather than abandoned. The practical effect is fewer half-finished imports and more of a site's pages actually making it into your knowledge base.

What changed under the hood

  • Automatic failover — if one route to crawl a page degrades, requests reroute to a healthy one, so a temporary outage on a single path no longer takes imports down with it.
  • Smarter retries — pages that hit a momentary error (a timeout, a brief rate-limit) are retried instead of dropped, so transient blips don't quietly shrink your knowledge base.
  • Steadier indexing — the step that stores and indexes crawled content tolerates brief interruptions, so pages aren't lost between being fetched and being saved.
  • Honest status — an import only reports success when content was genuinely captured, so a "ready" knowledge base really does have your pages in it.

What you'll notice

Most of this is invisible by design — the goal is that you simply don't think about crawl reliability anymore. When you import a site, more of its pages come through, large sites complete more often on the first try, and the occasional bad moment on the wider internet no longer means starting over. If a site genuinely can't be crawled, you still get a clear status rather than a silent partial result.

Why it matters

A knowledge base built from half a website teaches the AI half the story — and you'd never know which half was missing. Reliable import is the foundation everything else rests on: the more completely and dependably your sources come in, the more accurate and specific the outreach written from them. By making the crawler resilient to the normal turbulence of the web, we've made the knowledge your campaigns rely on more complete and more trustworthy, without asking anything extra of you.

Todas as novidades

Prospecção que continua quando você desconecta.Leads, emails, follow-ups e respostas, resolvidos.

Conecte caixas ilimitadas e deixe os agentes de IA encontrarem leads, escreverem cada email e fazerem follow-up. Ou envie seus próprios modelos no modo manual. A partir de $29/mês.

$1 por 3 dias · Cancele quando quiser · Sem contrato

Instalar com IA

Seu agente de código configura a CLI e as skills do FirstSales para você.

Prompt para Claude Code

I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code.

Read these first so you know how FirstSales works:
- Developer docs and API: https://developer.firstsales.io
- CLI: https://www.npmjs.com/package/@firstsales.io/cli
- Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md)

Setup
1. Install the CLI: npm install -g @firstsales.io/cli
2. Install the FirstSales skills:
   claude plugin marketplace add firstsalesio/firstsales-skills
   claude plugin install firstsales@firstsales
3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up.
4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need.
   Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden:
   read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY
5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to.

Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through:
1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product.
2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add.
3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own).
4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes.
5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads.
6. Inviting my team and giving each person the right access.

Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email).

Throughout, as you learn about my business, proactively suggest and help create:
- Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them.
- Campaign ideas and segments worth testing, with the reason for each.

Safety rules:
- Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes.
- Tell me before anything that spends credits, and how many.

Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options.