Check the Current Status in Chat and in the Dashboard with FORMLOVA

Last updated: April 28, 2026

When you operate a form, “what is the current state?” comes up constantly. But there are really two kinds of checks. One is a quick, one-off question such as “tell me the current situation in detail.” The other is a broader visual review of response lists, analytics, email settings, and form settings. FORMLOVA works best when those two jobs are separated: ask in chat when you want a quick answer, and open the dashboard when you want to look across the whole picture. This guide shows that split with a real example.

The parent MCP form service guide explains why FORMLOVA treats post-publish operations as part of the product surface. This guide narrows that idea to one practical question: when should you ask in chat, and when should you inspect the dashboard?

If you want the broader workflow across auto-replies, status checks, Google Sheets sync, notifications, and reminders, use the parent FORMLOVA form automation guide. It shows where "checking the current state" fits inside the larger automation loop.

For One-Off Questions, Chat Is the Fastest Place to Start

The first prompt in this example was:

Please tell me the current situation in detail.

FORMLOVA fetched the relevant analysis data and returned a summarized status report. In this example, that summary included:

basic form information
- title
- publish state
- access type
- number of fields
response status
- total responses
- status breakdown
- recent 7-day movement
performance
- views
- completed submissions
- conversion rate
- traffic breakdown
email
- whether auto-reply is enabled
- recent send activity
Google Sheets sync
- whether the integration is connected
- whether older responses are synced

That is exactly what chat is good at. It gives you the current answer quickly, without making you click across multiple screens first.

I think this is the right default for one-off checks. If your question is basically “what is going on right now?”, ask it in chat.

If You Want to See the Response Surface, the Dashboard Is Better

The response list is a good example of where the dashboard becomes more natural.

In the dashboard screenshot, the response table shows statuses, names, email addresses, participant counts, traffic source, and submitted time in a visual list. That is a different kind of understanding than a text summary. It lets you scan.

This does not mean chat is weak. Chat is still great for things like “show me only the people with participant count = 3.” But if you want to visually review the whole surface of the incoming responses, the list view is faster. The guide to view, filter, and update response status shows the chat side of that workflow in more detail.

That is the distinction I would give users: chat is for asking, dashboard is for scanning.

Analytics Also Follow the Same Split

The chat response already summarized the key metrics: total responses, recent growth, conversion rate, and traffic mix. That is enough if the goal is simply to know where things stand. If the next step is sharing or spreadsheet analysis, continue to the guide on how to export responses to CSV or sync them to Google Sheets.

But if you want to inspect trends and distributions visually, the analytics tab is more useful. In the dashboard example, you can see 30-day response counts, recent 7-day volume, daily submission charts, traffic sources, email delivery state, and field-level distributions.

That is why analytics follows the same rule:

ask chat when you want the headline numbers
open the dashboard when you want to interpret the patterns

I think that is a much more practical mental model than pretending one surface should do everything.

Email and Form Settings Are Easier to Confirm Visually

The same applies to settings.

In chat, it is helpful to hear that auto-reply is enabled or that Google Sheets is connected. That gives you a quick answer.

This is also important for form automation. Auto-replies, spreadsheet sync, notifications, and reminders are not one-time setup tasks. After launch, the team still needs a reliable way to ask what is enabled, what ran recently, and what needs attention. The FORMLOVA form automation guide covers that broader model.

But if you want to inspect exactly which email template is active, what the access restriction looks like, whether duplicate prevention is enabled, or what the current form settings are, the dashboard is the better tool. In the example screenshots, the email tab and the settings tab make those states much easier to confirm at a glance.

This is where the earlier product philosophy becomes operational. Work happens in chat. State confirmation happens in the dashboard.

This Is the Only Rule You Really Need

If you want the simplest version of this guide, it is this:

use chat when you want to ask for the current state
use the dashboard when you want to visually inspect the state

So prompts like:

Please tell me the current situation in detail.
What is the response status for this form?
Is auto-reply enabled?

fit naturally in chat.

But if you want to:

scan the response list
review graphs and distributions
confirm multiple settings in one view

the dashboard is the better fit.

That is the main takeaway I want this guide to give. FORMLOVA is not trying to force everything into chat. Chat is the primary surface, and the dashboard is the secondary surface for confirmation and overview. Once you understand that split, the product becomes much easier to use well.

Setup guide

Disclosure and Verification

This article is part of the FORMLOVA product blog. The author is the developer of FORMLOVA. Product facts, pricing, limits, and comparison claims should be checked against the current FORMLOVA spec, plan definitions, and relevant primary sources before publication or major updates. For privacy, hiring, legal, medical, or financial workflows, follow your organization's policies and specialist review.