Skip to main content

Pierre Chat as Your Dashboard Home

Learn how Pierre, FERMÀT's AI copilot, is now the dashboard home page so you can ask questions and take action without digging through reports.

Updated yesterday

What is Pierre Chat as Your Dashboard Home?

When you open the FERMÀT dashboard, the first thing you see is Pierre, FERMÀT's AI copilot. Instead of landing on a top-level page packed with KPI tiles, charts, and navigation, you land on a chat where you can ask Pierre any question about your tests, storefronts, or analytics, and get an answer with the supporting data inline.

This replaces the older information-dense home page. Brand managers and operators told us the data on the home page was the same data they'd ultimately drill into anyway, so the home page became a stop on the way to the answer instead of the answer itself. Pierre as your home page collapses that journey: ask the question you came in with, and Pierre returns the answer with the right session recordings, heatmaps, dashboards, or result cards already pulled up.

Now you can open FERMÀT in the morning and start with a question instead of a scan. Pierre also surfaces action items proactively, so you see new opportunities, anomalies, and reports waiting for you the moment you log in.

How to Use Pierre as Your Home Page

  1. Open your FERMÀT dashboard. You'll land on the Pierre chat home with the greeting "How can I help you today?" and an input field at the center of the page.

  2. Ask a question or click an action item. Type a question in plain language, like "where did mobile conversion drop last week?" or "show me top tests by AOV this month." Or click any of the Action Items cards below the input to jump into a Pierre chat that already explains the underlying anomaly, opportunity, or report.

  3. Review Pierre's answer and the inline artifacts. Pierre's response includes any relevant session recordings, heatmaps, dashboards, or result cards directly in the chat. Click any artifact chip to open it in the side panel.

  4. Use "Explore what you can do" if you're not sure where to start. The button in the top right opens a tray of ten capabilities Pierre can take action on, including spinning up a test, generating reports, automating workflows, drafting content, and managing connectors.

  5. Navigate to a specific page when you need it. Every page you used before is still available in the left sidebar. Pierre is the new front door, but every existing surface is one click away.

Use Cases

Triaging a sudden conversion drop. Your mobile CVR is down before standup. Log in, ask Pierre what changed, and get the affected pages, segment cuts, and supporting session recordings in seconds.

Reviewing a launch the morning after. Skip opening five dashboards. Ask Pierre "how did the new launch perform?" and get pacing, channel mix, and any flagged anomalies in one response.

Building inside the chat. Ask Pierre to spin up a test, draft a lander, or set up a new alert. Pierre takes the first cut and you iterate inside the conversation.

Reviewing the week without a meeting. Ask Pierre for the weekly performance highlights, what's outside expected ranges, and what to watch next week, all in one back-and-forth.

FAQs

Does Pierre as the home page change my analytics or attribution?

No. The underlying data, attribution model, and reports are unchanged. Pierre is a new interface on the same data.

Can I still go straight to a specific dashboard page?

Yes. The full left sidebar is always available. Pierre is the home page, not a replacement for direct navigation.

What happens to my saved reports and projects?

They stay where they are, accessible from the Projects section in the sidebar. Pierre can also surface them inline when relevant.

Does Pierre work with my existing tests and experiments?

Yes. You can ask about active tests, significance levels, and lift, and Pierre will pull the supporting data from the same place you used before.

Will Pierre take action without me confirming?

No. Pierre drafts and proposes, but actions like spinning up a test, publishing a change, or sending an alert always require your confirmation before they go live.

Did this answer your question?