N°01Support
How can we help?.
Answers for every module in the suite, in one place. Pick an app below, or write to us directly.
Still stuck?
Write to us and we'll reply within one business day.
Stack*form
Know every tool you pay for, who owns it, and what it costs this month.
No. Stack*form has no billing, bank, or credit card connection of any kind: every tool, cost, and renewal date is something a person enters, either directly in the app or through the public intake link. If a charge changes on your card, someone updates it here too.
There is no CSV or spreadsheet import today. Add tools one at a time from the Tools screen, or share your organization's public intake link so the people who actually use each tool can report it themselves, no login required; one submission can list several tools at once.
Not as a built-in field. A tool records the department that uses it and a monthly cost, but there is no per-client or per-project cost allocation; a team that needs that breakdown has to build it outside the tool today.
Anyone with an active Stack*form entitlement and a signed-in seat in your organization sees every record, cost included; there is no separate finance-only role that hides it from other seats. Signal*form staff can access it for support, the same model every module in the suite uses.
Nothing is sent anywhere. The renewal calendar sorts every dated tool into overdue, this week, this month, this quarter, or later, and it reflects the current state whenever someone opens it; there is no email, push notification, or text message today, so a person on the team has to actually check the screen.
Not yet. You can save a report template and set a schedule and a recipient list, but nothing currently sends it: generating and downloading the PDF is still a manual action today. Treat a saved schedule as a configuration for later, not a delivery you can rely on now.
Yes. The inventory, cost tracking, the renewal calendar, public intake, and approval workflows all work on a Stack*form-only account, and none of it needs another module turned on.
Metric*form
Every connected platform's campaigns in one place, with the AI-written analysis and the client-ready view already built.
Meta (Facebook and Instagram), TikTok, LinkedIn, YouTube, Twitter/X, Snapchat, and Pinterest connect through one account login. Google Analytics 4 and Shopify connect directly through their own account login, each scoped to one client. Google Ads campaigns can be added and tracked manually today; a live Google Ads connection isn't built yet.
No, for the ad platforms it does sync: every sync there is a button someone on your team clicks, with no scheduled or background sync running today, so those numbers are only as current as the last click. Google Analytics 4 and Shopify connect the same way, but the sync that would pull their numbers in isn't built yet, so a connected GA4 or Shopify account doesn't populate the dashboard today.
Metric*form doesn't cross-check or de-duplicate conversions between platforms today: each platform's campaigns keep that platform's own reported numbers, visible side by side rather than blended into one adjudicated figure. You can record which attribution model, last-click, first-click, linear, time-decay, position-based, or data-driven, your team has agreed is the standard for a client and mark it as the default, so the answer to which model you're using is written down, but reconciling the actual figures across platforms is still a step you do yourself.
Not a login, a link instead. Generating a portal link for a client gives them a token-based URL, branded with their own logo and color, that shows only that one client's campaigns. There's no username or password, and nothing on that link reaches any other client in your organization.
A platform sync pulls the trailing 90 days of campaign and creative-level data each time you run it; there's no way to reach further back than that today.
No. Every platform connection only reads from that platform's API; nothing in Metric*form writes a budget, pauses or resumes a campaign, or changes anything in a connected Meta, Google Analytics, TikTok, LinkedIn, YouTube, Twitter/X, Snapchat, Pinterest, or Shopify account. The AI analysis can recommend scaling, maintaining, reducing, or pausing a campaign's budget, but that's a written recommendation for a person to act on, not an action it takes itself.
Yes. Platform connections, creative-level analytics, AI-written analysis and forecasts, alert scanning, report templates, and the white-label portal all work on a Metric*form-only account.
No. Alerts surface in the app, in the alert bell and the alerts queue, when someone runs a scan; nothing is emailed automatically today. The same is true for AI-written analysis and forecasts: they're generated when someone asks for one, and nothing reaches a client until a person shares it, whether that's a report, a CSV export, or a portal link.
Spark*form
Turn a messy client conversation into a brief the whole team can actually work from.
Spark*form helps the strategist; it does not replace one. It removes the blank page and the formatting work, and its review pass catches vague or unsupported claims before the team sees them, but the strategic judgment in the brief is still yours to bring.
Today, Spark*form offers three built-in brief types (flash, creative, strategic) with strategy frameworks by vertical and audience, rather than an upload for a custom template. If your team has a fixed house format, compare it against the built-in structures before switching.
Client information pasted into a brief is scoped to your organization at the database level, with no path for another organization to query it; Signal*form staff can still access it for support, the same model every module in the suite uses. AI drafting, review, and persona calls send that content to Anthropic's and Google's APIs only when you trigger a generation; neither provider's training or retention policy for those calls is asserted anywhere in this product, so that determination rests with their account-level API terms.
Yes. Guided intake, AI drafting and review, personas, real-time collaboration, and export or client-portal sharing all work on a Spark*form-only account.
An approved brief exports to PDF, and you can share a public client portal link for sign-off that requires no separate login for the client.
English and Spanish today; pass the language when you run a review or generate a persona and Spark*form responds in that language.
No. Pushing a brief into Asana, Monday, ClickUp, Notion, Slack, or Teams is always a person clicking a button on an already-approved brief, never an automatic step.
Skill*form
See who can do the work, and how well, before you have to ask around.
Anyone with an active Skill*form seat can see every colleague's directory profile: name, department, position, skills, industries, languages, and career history, because that shared visibility is what makes the directory useful for staffing. Each person edits their own bio, skills, languages, and project history directly; only an org admin can set someone's manager or job level, enforced by a database rule rather than left to convention. There is no per-field privacy setting to hide part of a profile from the rest of the organization.
Yes, for the parts that need it today. One organization can define multiple agencies or offices alongside its departments, and employee profiles and services are tagged to a specific agency, so a holding company running several agency brands keeps one roster instead of a separate account per office. Time off and onboarding are shared org-wide today, not scoped per agency, so a multi-agency org runs one onboarding checklist and one time-off process across every brand.
Skill*form doesn't fill in a profile for you. Each person maintains their own skills, industries, languages, and career history; an admin can add a 'complete your profile' task to the onboarding checklist assigned to new hires, and an admin dashboard shows what share of the organization has a completed profile. There's no automatic reminder that chases anyone down.
Nothing today. Skill*form has no public-facing profile page, share link, or digital business card; every route in the product sits behind sign-in and an active Skill*form entitlement, so there is currently no way to share an employee's profile with anyone outside the organization.
No. Skill*form doesn't run payroll, calculate tax, or manage benefits enrollment, the core job of an HRIS; its own compensation records are explicit that they capture pay decisions, not a payroll process. What it replaces is the patchwork agencies build around a thin HR directory: a spreadsheet of who speaks what, a wiki for policies nobody keeps current, and a manual staffing process. If your organization already runs an HRIS for payroll and compliance, Skill*form runs alongside it as the skills, staffing, and internal-operations layer.
Yes. Profiles, directory, org chart, service matching, onboarding, time off, policy acknowledgment, documents, reviews, and recognition all work on a Skill*form-only account. Nothing here depends on another module being active.
The AI here drafts three things: a performance review narrative built only from the ratings and notes a manager already entered, a set of survey questions from a one-sentence intent, and a short summary of whatever analytics view is currently on screen. In every case, a person reviews and edits before anything is published, sent, or saved; the model never sets a rating, opens a survey, or changes a status by itself.
An employee sees their own current pay, band, and full pay history. A manager sees only a report's current pay and band, never their history. Beyond that, it's visible only to whoever an admin has explicitly granted compensation access to, not the wider organization by default, and pay history is append-only, so a correction adds a new record instead of editing over the old one.
Radar*form
Category research that takes a day instead of a fortnight, with sources you can check.
By default, with no key required: GDELT for press tone and volume, publisher RSS feeds, SEC filings, open academic and scholarly sources, and Wikipedia and Wikidata for entity resolution. The Meta Ad Library is also free, but only returns commercial-ad data where an ad's delivery reached the EU or UK, so it contributes little to nothing for a brand whose media runs in Latin America or the US specifically; Radar*form skips the check there instead of reporting a false empty result. A paid tier adds entity-resolved news, audience data, and social and creative-example providers once your organization sets a key for them.
Not from the free tier alone. Reddit is excluded because its free tier does not allow commercial use, and X currently has no usable free tier at all, so neither is read at any tier. Social conversation and creative examples become available once your organization configures a paid provider; until then, Radar*form's picture of a brand comes from news, filings, academic research, Wikipedia, and the Meta Ad Library.
Yes. Every finding in a report is written from sources and figures the model is handed, and each claim carries an id back to one of them. A citation that doesn't resolve to a source the model was actually given gets dropped from the report rather than kept with a caveat, so a claim that survives either has a real source behind it or it isn't in the report.
The free tier, on by default, reads GDELT, publisher RSS, SEC filings, academic sources, Wikipedia and Wikidata, and the Meta Ad Library, no key required. The paid tier adds entity-resolved news, audience data, social conversation, creative examples, and Google Ads intelligence, each one turning on only once your organization sets its own key for that provider.
Yes. Each report draws from your org's credit balance, which your plan includes and refills every month; unused credits roll over up to a cap rather than disappearing at the reset. Before you commit to running a report, Radar*form shows the exact cost in credits and how many your org has left, and if the balance is short, it says exactly how much and offers a top-up or lets you wait for the monthly reset instead.
Yes. Watchlist monitoring, category and AI-visibility tracking, multi-source research, cited synthesis, strategy framework workflows, collaborative review, and export or portal sharing all work on a Radar*form-only account.
You choose: weekly, monthly, or manual, run by hand whenever you want a fresh read. A monitor emails you only when the data shows a real change against its baseline, not on every scheduled check.
Yes. Ask a follow-up question against a finished report and get an answer grounded in that report's own sources, without opening a new workflow or starting the research over.
Flow*form
See what the agency is committed to, who is doing it, and whether it is making money.
Longer than a five-minute import, because there isn't one. Adding your clients, projects, and a rate card is manual entry, so plan on a few hours to get active work and your team into Flow*form correctly. Profitability and the deviation flag only start reporting real numbers once a project has a budget, a resolved rate, and a first week of logged time behind it.
Not today. There's no import path from Asana, Monday, ClickUp, or any other tool, so existing projects and tasks are entered by hand. If a project is already underway when you switch, plan to re-create the active work rather than migrate it.
Whoever your admin grants it to. Flow*form ships named permission presets: Finance and Account Director see margins and financial data across every project, Project Manager sees delivery data but not cost rates or financials, and Contractor is blocked from financial data entirely. Cost rates specifically are visible only to an admin, the rate's own owner, or someone explicitly granted that view, enforced at the database level rather than just hidden in a menu.
Yes, if they log time or are assigned work. Flow*form is seat-based, and a contractor who logs hours or sees their own tasks needs a seat like anyone else, though the built-in Contractor preset limits what that seat can see to their own bookings, tasks, and time, with financial data blocked. A client doesn't need a seat: they reach a status page through a token-scoped portal link with no login to manage.
You can run projects and capacity without it, but not profitability. Margin is computed from logged time against a resolved rate, so a project nobody logs time against shows no margin rather than a number to act on. Approval on submitted timesheets is off by default specifically because gating logging behind an approval step measurably reduces how much gets logged.
Yes. Projects, tasks, capacity, time tracking, budgets, profitability, the client portal, and the PM agent all run on Flow*form's own data and work fully on a Flow*form-only account.
Client financial information stays scoped to your organization at the database level, with no path for another organization to query it, and access to financial data specifically follows the permission preset your admin assigns, down to blocking it outright for a Contractor seat. AI features read that data only when a chat turn or a scheduled agent job actually runs, and Signal*form staff can still access it for support, the same model every module in the suite uses.
Brain*form
Ask a question about any client and get an answer with the exact source attached.
Client content reaches Anthropic's API only when someone in your organization asks a question or requests an insight, never on a schedule or in the background; embedding a document for search happens inside Supabase's own infrastructure and never reaches Anthropic at all. The answer model requires your organization's connected Anthropic account to run on a 30-day data retention setting, which is an account-level term set by Anthropic, not a policy this product asserts, controls, or can override.
Not through any path the product exposes. A client's login reads only through curated views built to leave out internal content and filter to their own records, with no view at all for providers, provider grades, private notes, or the sharing log; the client's own question-answering feature runs through a separate external Ask function built from those same restricted views. An adversarial test suite logs in as a client and checks that none of that internal content is reachable, on every release.
PDF, Word documents, plain text, and markdown files today, uploaded per client and tagged with the language they're written in. There's no meeting-recording or calendar connector yet: everything ingested comes from a file someone uploads.
Yes, with one honest limitation. Keyword search matches Spanish content at full strength, and every stored record and citation displays correctly regardless of language. The similarity search that ranks documents by meaning runs on an English-only embedding model, so a Spanish document's meaning-based ranking is currently weaker than an equivalent English one; the keyword side of search does not share that gap.
Yes. Document ingestion, search, cited answers, the client record and graph, the client portal, and sharing controls all work on a Brain*form-only account, built from whatever your team uploads and records itself.
Whatever they logged, uploaded, or answered a question about stays in the client's record after they're gone, and a replacement can ask the same questions and get the same cited answers instead of starting from a shared drive. Brain*form only knows what was put into it, so the earlier that starts, the less this problem costs later.
Yes, for support, the same access model every module in the suite uses. That access is separate from and does not widen what any client's own portal login can reach, since the portal path is built from curated views with no internal-access route built into them.
Pulse*form
Start the day already knowing what's urgent, who's waiting on you, and what you actually got done.
No. Every reply it drafts lands in the approval queue as pending, never sent, even if you tell the chat agent to send it directly; that instruction is built to refuse and queue the draft instead. Approving a draft starts a 60-second window where you can still undo it before it goes out.
Nobody. Your brief, tasks, and drafts are scoped to your own account at the database level, and unlike other modules in the suite, Pulse*form's tables carry no standing staff-access path: nobody on the Signal*form team can open another person's brief through the product. Your manager doesn't get a copy, and a colleague on the same account can't search your mail.
No. Pulse*form has no connection into Brain*form, Flow*form, or any other shared view in this suite today, and that boundary is enforced in the code, not left to a setting. The suite's own rule is that a person's mail can only ever reach a shared surface if that person sends one specific item there themselves; nothing does that automatically, and nothing does it at all today.
It reads the last day of your email, tomorrow's calendar events, and your open tasks, once a night. It does not read chat messages from Slack, Teams, or anywhere else today. It never reads another person's account, and it never permanently deletes anything in your mailbox.
The stored credential is deleted immediately, from a table your own signed-in account could never read in the first place, not just marked inactive. Your existing briefs, tasks, and chat history stay until they age out on the normal 30-day schedule; reconnecting later starts a new credential the same way the first connection did.
Removing your seat ends your access to Pulse*form itself right away. The mailbox connection is a separate thing: disconnect it yourself before you go, or revoke it from inside your Google account's own settings, and the next scheduled sweep fails safely and stops trying rather than continuing against an account that no longer grants it access.
No. A single seat with no other module turned on gets the full daily brief, the retrospectives, chat, and the approval queue; none of it depends on anything outside your own connected account.
Not yet. Today Pulse*form connects to Google: Gmail, Calendar, and Tasks. Microsoft support is built the same way and is marked coming soon in the app.
All systems operational