Skip to content
figbotGet started

Hosted answer pages

Send a page that answers back.

It works like a deck. Your team writes the answers it already gives; the page covers everything else from your own knowledge, in the same layout and your own brand. A visitor cannot tell which slides were pre-built.

Get startedSee how it answers

Invite-only while we finish it — open to the fig1 team, and to anyone holding an invitation.

For marketing teams running campaigns, sales teams sending decks, support teams answering the same enquiry twice a day, and agencies keeping clients apart.

Every page gets its own address: page.fig1.ai/b/your-workspace/your-page

page.fig1.ai/b/northwind/tea-sales
NorthwindLive

Overview

Northwind in numbers

2 days
To a first campaign
98%
Answered without a human
12,000
Teams on Northwind
Chat

Ask Northwind anything, or walk the deck.

Look

A demonstration, not a live page — built from the same parts a real one is.

Why a page

A deck cannot be asked anything. A widget cannot be sent.

Which is why so much of a sales conversation happens twice — once in a deck nobody can question, and again in a thread nobody signed off.

What a prospect is actually sent

A chat widget
Answers the question asked
Yes
Says the thing you decided to say
Sometimes
Wears your brand
A colour
Is a link you can send
No
Reads on a phone
Yes
A slide deck
Answers the question asked
No
Says the thing you decided to say
Yes
Wears your brand
Yes
Is a link you can send
As an attachment
Reads on a phone
Badly
A figbot page
Answers the question asked
Yes
Says the thing you decided to say
Yes
Wears your brand
Yes
Is a link you can send
Yes
Reads on a phone
Yes

Answering

One page. Three ways it answers.

A widget waits to be asked and improvises. A deck says exactly what you decided and cannot be asked anything. figbot does both, and a visitor is never shown the seam.

Where an answer comes from

A slide somebody wrote

Your team authors the answers it already gives. A visitor walks them with arrow keys, the controls in the corner, or a swipe.

A rule somebody aimed

Point a keyword at a slide, or a visitor's context, or a few ways somebody might ask. The question lands on the slide you chose, and the rail says the sentence you wrote.

The page, composing

Anything you did not cover is answered from your own knowledge base, in the same layout as the slides around it.

A keyword rule answers for nothing
Point a keyword at a slide. On a hit the deck jumps and the rail says the sentence you wrote — no model call, and nothing to wait for.
A rule can read the visit
Match on locale, referrer, landing path or campaign parameters, so a visitor arriving from an ad opens on the slide that ad promised.
A rule can match what somebody meant
Give a rule a handful of example phrasings and it fires on anything close to them, so “how much is this going to run me” reaches the pricing slide without anyone having written that sentence.

Use cases

One page per audience, not one per company.

One account in full — a winery, because its audiences share almost no questions. A software company has the same shape the moment pricing, onboarding and partners stop being one page.

  • page.fig1.ai/b/stonecrop/wine-club

    Members

    What is in the spring shipment, how to skip a release, how to change a shipping address, what the member price is — answers somebody on the team already writes by hand every week.

    Where the link goes. The Membership link in the nav, the welcome email, and the renewal notice.

  • page.fig1.ai/b/stonecrop/wholesale

    Trade buyers

    Case pricing, which states have distribution, tech sheets, sample requests. A plainer deck than the consumer page — a buyer comparing three producers is not reading the story.

    Where the link goes. A rep's email signature and the trade page. Not the shop, where a case price is a support ticket.

  • page.fig1.ai/b/stonecrop/weddings

    Event enquiries

    Capacity, seasons, minimums, what the site fee covers, which dates have gone — the first four emails of every booking, and none of them needs a person.

    Where the link goes. The Events page, and the automatic reply to the enquiry form.

  • page.fig1.ai/b/stonecrop/rose-release

    One campaign

    One release, one deck. A rule reads the campaign parameters, so a visitor from the rosé ad opens on the rosé slide and one from the newsletter opens on the story.

    Where the link goes. The ad's destination, and a QR on the neck tag. Paused the week it sells through, which is the week it stops costing anything.

Author the ten answers you already give
The questions you can predict are the ones that should never wait on a model. Write them once as slides, aim keyword rules at them, and let the page compose only what you did not cover.
Let the campaign choose the opening slide
One release page opens on rosé for the ad and on the story for the newsletter, without being two pages.
Pause it when the campaign is over
A paused page is not answering and is not billed, so a page per release costs what the release costs.
A visitor who comes back can keep it
A page installs from the browser’s own offer, and an installed page opens like an app.

Authoring

Say what you want changed — or move it yourself.

Open a page in the console and describe the change. The stage re-renders as the answer, with one step of undo.

figbot · editing “Northwind”

Make it darker and put pricing second

  • DesignDrafted

    Palette switched to a dark ground with a lit horizon.

  • DeckDrafted

    “Plans” moved to slide 2. Two triggers still point at it.

Undo thatOr drag it yourselfAttach a file or a page
Or edit it directly
The slide on the stage is the slide being edited. Drag an item where you want it, set its size and colour in the rail beside it, reorder from the navigator down the side.
Hand it a file
Images and video go onto a slide, a PDF into your knowledge base. Name a page and it takes the words — and the colours and typefaces too, so “match our brand” is a sentence rather than a project.
Nothing reaches a visitor by accident
The deck and the design stay drafts until you publish. Revise at 2pm and the prospect reading at 2:01 still sees what you published.
A new slide starts from a shape
Shapes named by what a slide has to say — open the deck, show the product, put the plans side by side, let a customer say it, ask for the next step. 27 of them, and the gallery draws the slide before it adds it.
Or arrange one yourself
Text, buttons, images and video, dragged and resized on a 16:9 stage. What you arranged is what a visitor gets — on a laptop, beside the chat rail, or on a phone.
Nothing ships with a hole in it
A template lands with its blanks showing, and unfilled blanks are counted on every slide’s row and beside the Publish button — so no deck goes live carrying a placeholder quietly.

Design

It wears your brand, three levels deep.

Palette, type, shape and texture, set for the whole deck at once — from a gallery of 8, from a form, or from a sentence.

LedgerNavy and warm white, serif headlines. Reads as considered.
MidnightDark, with a lit horizon behind the deck. Good for a launch.
EditorialAll serif, generous margins. A deck that reads like a page.
SignalHigh-contrast black and a bright accent. Loud on purpose.
The deck sets the look
One design decides the whole page, including the chat rail — because a navy deck beside a grey rail is two products on one screen.
A slide may disagree with it
Hand one slide its own colours, typefaces or type size. Every field it leaves alone follows the deck, including changes you make to the deck later.
An element may disagree with the slide
On a hand-arranged slide the control goes down to the item: its own size, colour, face, italics.
And what escapes is counted
Every colour, face and size that has stepped outside the design is counted and shown where you are changing it. “I changed our brand colour and three slides did not change” should not be something a customer discovers for you.

Knowledge

It answers from what you already wrote.

Upload your documents and the page answers from them. Until you do, it answers from the fig1 site it is linked to — there is no flag to flip and nothing to keep in step.

No web search, deliberately
A sales page that answers a pricing question out of a search result instead of your own documents is worse than one that says it does not know.
One knowledge base per workspace
An agency runs one workspace per client, so holding one client’s documents never exposes another’s. Two audiences that must never read out of the same documents are two workspaces.

What it costs

You pay for the pages that are live, and what they answer.

Metered per page and per answer, after the fact. No seats to buy in advance and no plan to size — the invoice counts the days each page was live and the answers it gave.

Drafts and paused pages are free
Build five and publish the one that reads best. Run a campaign page for six weeks and pause it the day the campaign ends.
No new account
figbot uses your fig1 sign-in. If one of your sites has figbot enabled, your workspace is already there.

Questions

What people ask before they build one.

Eight that keep arriving, answered here in writing rather than on a call later.

Does a visitor need an account?
No. A page is an address, so it opens the way any link opens — nothing to install, nothing to sign in to, no app. A cookie on the page's own domain remembers the conversation for thirty days, so somebody who comes back is not starting again.
Can I put it inside my own site?
Yes — the whole page, set into yours, and never a chat widget in the corner. An owner lists the sites allowed to show your pages, and the Share dialog then gives you the code to paste, including a version that carries your page's campaign tags into the frame. On any site that is not on the list, a page still refuses to load inside it.
What does it do when it does not know?
Says so, and offers to put the visitor in touch with somebody. Every page is told never to invent a price, a date or a feature, and there is no web search behind it to improvise from — so the failure you get is an answer you have to write, not one a customer has to correct.
What if it answers something badly?
Write the answer you wanted as a slide and point a keyword at it. That question stops reaching a model at all — the deck jumps to your slide and the rail says your sentence — so a page gets more predictable the longer you run it, not less.
Can a visitor leave their details?
A slide can be a form. What somebody sends is recorded against that page and emailed to you, kept with the consent sentence they were actually shown rather than the one that is on the block today.
Can I see what people asked?
Every page has an inbox: the enquiries first, then every conversation it has had, in full. It is where you find out which objection keeps arriving and whether the slide you wrote for it is being reached. Reading is all it does — figbot does not reply to anybody on your behalf.
Who can see a page before I publish it?
Only your workspace. A draft is a 404 at its own address, and so is a paused or an archived one — there is no unlisted state, and no link that quietly works early.
Can I start from the deck we already have?
Upload the .pptx. The words come across, so do the pictures inside it — filed as workspace images you can put on any slide — and so does the theme somebody chose, the palette and typefaces every deck in the company inherits. The layout does not: slides are rebuilt as figbot's own shapes, which is what the design gallery is for.

Getting started

Build one this afternoon.

Four steps, and nothing is live until you publish — so all of it happens before anybody outside your team sees a thing.

Building one

  1. Create the page

    A name, a greeting and a slug. Your workspace plus that slug is the address, and the address is the product.

  2. Author the deck

    Add slides from shapes named by what they have to say — or describe the change and watch the stage re-render as the answer.

  3. Give it a look

    Pick a palette from the gallery, fill in the form, or write a sentence. One slide is allowed to disagree with the rest.

  4. Publish

    The draft becomes the page. Edit it again tomorrow; today's visitors go on reading what you published.

Nothing is billed until a page is live, and a draft is a 404 until you publish it. Build five and publish the one that reads best; pause a page the day its campaign ends and it stops costing anything that day. There is no plan to pick and no seats to buy in advance, so there is nothing here to size wrongly.

Every page gets its own address.

figbot uses your fig1 sign-in — no second password. Open your workspace and the pages you already have are there.

Open your pages