Autopilot

Autopilot is the chat workspace available throughout your dashboard. Open Autopilot at the top of the sidebar, choose an existing conversation or start a new one, then type or dictate what you need.

Each conversation is private to your user account. You can reopen, rename, or delete it from the conversation list.

When you open Autopilot for the first time in a browser tab, it continues your newest conversation if that conversation was active within the last 30 minutes. After a longer gap, Autopilot starts a fresh conversation using your preferred model. Your older conversations remain available in History, and opening a specific conversation always takes you to that conversation regardless of its age without changing your preference.

When Fondaro will ground the next turn with a specific record, the empty composer names it in plain language: Ask about this lead or Ask about this call. Other views keep the general prompt because they select the relevant capabilities rather than sending every field visible on the page. This context does not grant extra access: your normal role and record permissions still apply.

Who can use it, and what it can see

Autopilot is available to everyone in your organization, not just admins.

It works with your own signed-in identity, so it sees exactly what you see everywhere else in Fondaro. If you are a member, that means the leads, deals and tasks assigned to you. If you are an organization admin, it means the whole organization.

A few things are admin-only and simply will not appear if you are a member: changing who owns a lead, changing the status of many leads at once, creating or editing Loops, and reading or building the organization website. Changes of any kind also need an active subscription, so without one Autopilot can read but not propose.

Your identity and branding

Every Autopilot turn receives your organization's current branding and the signed-in team member's identity before the model runs. Customer-facing copy uses your agency name, description, languages, contact details, logos, and the current rep where those values are configured. Fondaro is the software provider and is never used as a fallback agency, sender, team name, or email sign-off.

An email proposal resolves its envelope on the server rather than asking the model to invent it. The review card shows the exact From and To email addresses, the rep's name and avatar, and the organization behind the sender. Autopilot will not create an email proposal unless the lead has an email address and your organization has a verified sending domain, and it refuses customer email copy that presents Fondaro as the sender, agency, team, or sign-off.

What Autopilot can do

Autopilot can now work across most of Fondaro:

Leads. List and search them, read a full brief, read the whole activity timeline, count the pipeline, and read your tag catalogue and team roster.
Lead changes. Create a lead, correct contact details, move a lead's status, and set tags. Admins can also change who owns a lead and move many leads at once.
Tasks and notes. List them for a lead, add one, edit one, delete one.
Deals. The whole pipeline: list and open deals, create one, edit it, move it between stages, close it as won or lost, and reopen it.
Calls and emails. Read a lead's call history, the stored transcript and AI analysis of a specific call, and the email history. It reads only what has already been generated, so asking for a transcript never starts a new transcription.
Properties. List your connected sources, resolve a place name, search listings, inspect a visual contact sheet, and refine the results into a buyer-specific shortlist.
Brochures. The full lifecycle: create one, edit its details, add, remove, reorder and refresh listings, correct a listing's location or facts, revoke and renew the share link, and delete a brochure.
Reports. Read the metric catalogue, build a saved CRM report, and freeze a snapshot so the numbers it quotes are the numbers you see.
Dialling. Queue an ordered list of leads for a power-dial run. Autopilot never places a call; your own browser does that.
Loops. Admins can read the node catalogue and create or update Loops.
Website. Admins can read the current site and preview state, then prepare a brand takeover, ordinary change, language addition, or failed-preview repair. The build starts only after Build preview is approved.

Reads run immediately and come back as compact cards. Every card links to the page that owns the record, so you can go straight there when you need the full picture.

Property searches also give you two direct next steps. You can refine the results into a shortlist, or ask Autopilot to prepare a brochure and email. A broad first page is treated as discovery rather than as a recommendation: if the buyer, budget, bedrooms, or another important criterion is missing, Autopilot asks for that before claiming a property is a strong match. Generic brochure requests remain editable proposals. During completed-call review only, the grounded brochure is created automatically; the note, status and email stay pending, the email already contains the real link, and an explicit refinement updates that same brochure.

Try requests such as:

"Show my pipeline."
"Which of my leads have not been contacted in three weeks?"
"Summarise the last call with the Andersson lead and what I promised them."
"Move the Marbella villa deal to negotiation."
"Search my connected sources for three-bedroom villas in Marbella under 900k."
"Build a brochure from those three and set the recipient to Sofia."
"Prepare a follow-up task for that lead next Tuesday."
"Build a Loop that drafts a welcome email when a new lead arrives."
"Change the website homepage to lead with our beachfront listings."

Review before anything changes

Autopilot never changes your data as soon as you ask. It puts a card beside its reply, and nothing happens until you approve it.

There are two kinds of card.

Editable cards for a task, a CRM note, an email, a new brochure, or safe website request fields. These show the fields and let you correct them before approving. An email card keeps its server-resolved From and To identity read-only while you edit the subject and body, and previews the CRM signature that will be appended. Use Edit signature on the card to change it in the existing signature editor. Its action says Send email because approval sends it; the card says Sending until the server confirms delivery. A website card uses Build preview and discloses that approval starts one metered builder turn.

Change cards for everything else. These are a summary of what will change: the record it affects, what it is now, and what it becomes. They are deliberately read-only. If something is wrong, reject the card and ask again rather than editing it, so what you approve is always exactly what you reviewed.

To resolve a card:

Check the record it names, and open it if you want to see more.
Read the before and after values.
Choose Approve to apply exactly what the card shows, or Reject to leave Fondaro unchanged. For an email, choose Send email instead.

Approval runs the same business rules as the equivalent action on the page itself. A proposal cannot be approved twice, and the decision and its result stay beside the original message, including after you close and reopen the conversation. Approved, rejected, and failed cards keep their final state instead of offering the action again. A completed CRM proposal card names the team member who approved it, shows their account avatar, and records Autopilot plus the exact model that prepared the turn when that model attribution is available.

Two behaviours worth knowing:

Changes that cannot be undone are marked. Deleting a task, note or brochure, revoking a brochure link, and changing the status of many leads at once all carry a warning and a distinct confirm button.
If the record changed while the card was sitting there, approval fails. Rather than overwriting whatever someone else did in the meantime, Autopilot tells you it changed since it was proposed. Ask again and it will read the current state.

An email proposal is not sent while it is pending. Choosing Send email rechecks your current access, the lead's current email address, and the reviewed organization sender. If they still match, Fondaro sends it through your verified domain, applies your CRM email signature, and records it in the lead's email history and timeline. If anything changed, sending fails and you must prepare a fresh proposal.

Choose a model

Your first conversation starts with Auto, the recommended choice. You can choose a different model at any point. Fondaro starts a new conversation with that model automatically, saves it as your preference for this organization, and keeps the previous conversation unchanged in your history. New conversations started elsewhere in the dashboard and background call reviews use the same preference, including after a cold browser load. Choose Auto to make Auto your preference again.

Auto is deterministic. It uses the first available model in Fondaro's approved list, and the model control keeps that model's name visible beside Auto. It does not balance a turn dynamically between models.

The searchable selector groups the approved models into Flagship, Balanced, Fast, and Free sections. Each row shows the provider, model name, an input capability summary, and Fondaro's effective input and output prices per one million tokens in your billing currency. These are the customer rates after Fondaro's configured pricing has been applied, not the provider's base cost. Cached input and cache creation have their own prices when the live catalog supplies them.

A Free label appears only while every live token price for that server-designated free model is exactly zero. If any of those rates changes, Fondaro removes the model rather than presenting a paid model as free.

Token rates are displayed as standard two-decimal currency values, while the usage ledger and payment meter store whole cents. Each model step with a positive cost rounds up once to the nearest cent. The selector shows this rule beside the rates. If live prices cannot refresh temporarily, it labels the last saved snapshot as stale; it never estimates a replacement rate in the browser.

Models can accept different inputs. Laguna is text-only, so it cannot be selected while a draft or the conversation contains images. When Laguna is selected, the composer blocks image selection, drag and drop, and pasted images. The server checks the same capability again before any provider call.

Laguna is also the one model for which Fondaro does not enforce a no-training provider route. Its May train label explains that Poolside may use the conversation and CRM context for model training. Fondaro keeps the no-training safeguard enabled for every other model. If Auto ever resolves to a model with the same policy, Auto shows the same label.

When Auto is selected, each answer names the model that actually produced it. Explicitly selected models are named on answers when a conversation contains more than one model, so you can tell them apart later.

The available list comes from Fondaro's live model catalog, so names can change as models are evaluated or become unavailable. If a model is not covered by your plan, the reply is replaced by a short note naming that model and your conversation is kept. Choose another model and send again.

Dictate a message

Choose the microphone in the composer and record your request. Fondaro turns the recording into text in the composer. Review or edit that text, then send it like any other message. This is dictation, not a voice call or a spoken assistant session.

Background work

Most Autopilot turns finish inside the open conversation. Work that genuinely detaches is followed on the surface that owns it: website builds on Website, CRM exports on Migrations, and video renders on the ad you started them from.

Website work is durable after approval. Closing the dock or navigating away does not cancel it. Its compact work card restores a safe phase when you return, while the Website preview remains the source of truth. See Build your website with Autopilot.

Ordinary answers, reads, and proposals are not background work. Keep the conversation open while a response is generating. If a turn is interrupted, use Retry or Regenerate. Use Stop when you want to end the current response.

Current limitations

Autopilot can only use the capabilities listed above. It does not have unrestricted access to every Fondaro screen or API operation.
It does not send email without your explicit approval, dial a phone, publish a website, or approve its own proposals.
Long call transcripts and email bodies are shortened before Autopilot reads them. When the exact wording matters, open the record.
Autopilot can prepare a property selection for a lead you identify. It does not yet rank your whole CRM against listings automatically, because buyer preferences are not stored as one consistent structured profile across every lead.
A change card cannot be edited. Reject it and ask again.
Autopilot can queue a dial session, but it cannot pause, resume, advance or stop one. Use the dialer's own controls for that.
Dictation only fills the text composer.
Loop authoring is admin-only. Autopilot creates a new AI-authored Loop paused for review and links you to its editor.
Loop runs are followed in the Loop editor.
Website building is admin-only, creates a preview rather than publishing, and allows one active builder turn per organization.