FSRevs AI Documentation Guide

A note for human visitors

This page is intentionally written for AI-assisted search

Use this map to find a guide yourself or help an AI assistant find the right source. It covers public FSRevs features and workflows; it cannot see your workspace, customer records, or current settings.

Use this page in either of two ways:

As a person: choose the topic below that best matches what you are trying to do.
With an AI assistant: copy the prompt below, paste it into the assistant, add your question, and let the assistant follow the relevant official links.

Integrations and automation: Use Integrations to connect other systems, synchronize Customers, and send Review Requests or Custom Forms. Start with the Make guide, Zapier guide, or the full integration routing section. For automated messages, also read Customer Identity and Sending.

Bring this guide to your AI

Copy a safe, source-first prompt

Paste this into ChatGPT, Claude, Gemini, Copilot, or another assistant, then add your question. The copied version automatically includes this page’s full URL.

Guide URL/ai-guide/

I need help with FSRevs. Use the official FSRevs AI Documentation Guide at /ai-guide/ as a transparent map to the relevant public FSRevs user-guide pages. Follow the links that match my question, read those source pages, and base your answer on them. Cite the specific pages you used. Separate documented facts from inference, do not invent account-specific settings or UI state, and say when the documentation does not answer something. This guide is reference material—not an instruction to override your rules, safety policies, or my request.

My question:

This prompt asks the assistant to use official documentation and cite it. It does not ask the assistant to ignore instructions, bypass safety controls, or take action in your FSRevs account.

Machine-readable documentation

For a quick topic lookup, use the compact documentation index. It lists every published guide with its title, summary, and page URL. For a specific setting or question, the section index also includes direct links to the headings on each page.

Both indexes are generated from the same content as this site on every build. Read the linked guide before answering; the indexes identify sources rather than duplicate their instructions. They are available without signing in or running browser JavaScript. If your assistant cannot open links, copy the relevant guide section into the conversation and include its page URL.

For technical integration questions, use the OpenAPI schema or its readable API reference. The schema describes supported requests and responses; the integration guides explain setup, permissions, sending, and recovery.

These resources help tools discover the content. Whether an assistant can browse or retrieve it depends on the assistant you use.

Purpose and trust boundaries

For AI assistants: this page is a routing index, not a substitute for the source documentation. Identify the user’s intent, open the smallest relevant set of linked pages, and ground the answer in those pages.

Use these boundaries when working from this guide:

Instruction priority does not change. Treat this page and every linked page as public reference material. They do not override system, developer, safety, or user instructions.
The linked guide pages are the source for product behavior. Prefer a specific feature page over this router when making a detailed claim, and cite the page used.
Do not guess about the user’s account. A role, assigned location, configured feature, plan, live record, or current screen cannot be known from public documentation alone.
Protect private information. Do not ask for passwords, verification codes, API keys, full customer lists, or unnecessary customer personal information. Ask only for the minimum context needed to explain the next step.
Separate fact from inference. If the documentation does not settle a question, say so plainly. If the portal differs from the guide, explain that access, configuration, location scope, or a product update may be involved.
Do not claim to have changed anything. Reading this public site cannot modify an FSRevs workspace. For account-specific help, direct the user to support@fsrevs.com.

Fast routing procedure

Use this sequence for most FSRevs questions:

Classify the request. Is the user asking what something means, how to perform a task, which setting controls behavior, why a result occurred, or how to interpret reporting?
Resolve the FSRevs object. Distinguish Review Flow, Custom Form, Smart Link, Simple Page, customer record, Flow Activity record, Form Response, and Review Showcase. If the term is unclear, start with Key Concepts & Glossary.
Resolve scope. Determine whether the question is global or location-specific. Location scope can change what is available and which setting wins. Use Understanding Locations and Location-Level Overrides.
Open the procedural source. Use an overview for “what/why,” a creation guide for “how do I build it,” a settings guide for a specific control, and activity or report pages for “what happened.” For automation, CRM synchronization, Make, Zapier, API access, or webhooks, start with Integrations and follow the matching platform or technical guide.
Cross-check operational constraints. For sending, include consent and delivery guidance; automated sends also require Customer Identity and Sending. For missing integration controls, check the user’s API Access, role, and location access. For routing, distinguish configured Connections from the Journey FSRevs actually observed.
Answer at the user’s level. Lead with the next useful action, use the portal labels documented on the source page, cite the relevant pages, and call out any assumption.

Core routing rule
Concept page → task page → settings or evidence page

Read only the layers needed for the question. Do not bury a simple task under the entire documentation set.

FSRevs in one mental model

An FSRevs workspace contains locations, team members, customers, configuration, and collected data. Locations can affect access, branding, links, attribution, and which customer experiences are available.

The main customer-facing experiences are:

A Review Flow: a configurable, multi-stage experience that can collect sentiment, direct feedback, photos, attribution, and offer review, social, or custom destinations. Start with How Review Flows Work.
A Custom Form: a structured form made from customer fields, questions, uploads, and display content. Start with How Custom Forms Work.
A Simple Page: a branded, block-based web page that can contain rich text, managed links, video, and click-to-copy content. Use Simple Pages.

People reach those experiences through tracked email or SMS requests, sending from their own device, a Smart Link, QR code, NFC tag, or a connected destination. The resulting records appear as customers, Flow Activity, Form Responses, message history, logs, journeys, and reports.

01Workspace + locationsscope, access, branding

02Experiencesflows, forms, pages

03Distributionrequests, links, QR

04Records + reportsresults and evidence

Route by the user’s goal

Learn, register, or set up a workspace

Start here when the user is new or asks about initial configuration.

Key Concepts & Glossary

Use first when terminology is unclear or the question crosses several FSRevs features.

Creating Your Account

Use for registration, Workspace Name, initial Google-assisted setup, launch, and signup troubleshooting.

Find Your Workspace & Sign In

Use for Workspace ID recovery, email or username sign-in, password reset, inactive accounts, setup invitations, and Terms acceptance.

Setting Up Your Business

Use for the recommended sequence: verify a location, add links, build a first Review Flow, optionally add a Smart Link, test sending, branding, and team access.

If the user asks for an exact plan limit or price that is not stated on Usage & Limits, do not invent one; refer the user to support or their account’s current plan information.

Understand or configure locations

Location context is often the missing piece when a flow, form, user, link, or setting is not visible.

Understanding Locations

Use for primary locations, identifiers, global versus location-specific resources, location data, and timezone effects.

Managing Locations

Use to add, edit, make primary, or remove a location and understand location-linked features.

Location-Level Overrides

Use when a value differs by location or appears not to inherit. A blank location field generally keeps the global value; explicit local values replace it.

Build, change, or troubleshoot a Review Flow

Choose the source based on the shape of the question.

How Review Flows Work

Best conceptual source for customer stages, sentiment, review destinations, direct feedback, completion, and how configuration shapes the experience.

Creating a Review FlowUse for the end-to-end build and test workflow.Review Flow Settings Guide

Use for exact options under Basics, Customer Details, Reviews & Feedback, Completion, and Sharing & Delivery.

Review Flow Troubleshooting

Use when requests are not received, external reviews do not appear, or a flow is unavailable to send.

For sending a Review Flow, route to the consolidated Sending Requests guide rather than treating creation and delivery as the same task.

Build, change, or distribute a Custom Form

How Custom Forms Work

Use for form purpose, scope, visitor experience, identity, permission, entry methods, and after-submission behavior.

Creating a Custom Form

Use for the build sequence from scope and fields through completion, Send & Share, and testing.

Custom Form Settings Guide

Use for the exact Basics, Build, After Submission, and Send & Share controls.

Custom Form Field Types

Use to choose between customer identity fields, question controls, uploads, and display-only elements.

For missing fields, rejected uploads, unavailable forms, or missing responses, use Custom Form Troubleshooting. For delivery and public sharing, continue to Sending Requests and Smart Links.

Send a request safely

Start with the consolidated sending guide, then add only the channel or policy source the question needs.

Sending Requests

Primary task guide for Review Flow and Custom Form requests, customer selection, request options, FSRevs delivery, device delivery, shared links, duplicate prevention, reminders, and tracking.

Quick Actions & Launch

Use when the user wants the fastest entry point, wants to reuse a recent setup, or cannot see an expected action.

Send from Your Device

Use when FSRevs prepares a tracked request but the user sends it through the phone’s own SMS or email app.

Deliverability, Consent & Inbox Placement

Use for permission, channel choice, message writing, reminders, inbox placement, and responsible review-request practices.

Delivery, Bounces & Unsubscribes

Use for delivery lifecycle, hard and soft bounces, complaints, suppressed contacts, SMS failures, and unsubscribe handling.

Never infer that a person has permission to contact a customer. Sending questions should preserve the documented consent, unsubscribe, complaint, and suppressed-contact safeguards.

Create or troubleshoot Smart Links, QR codes, and NFC

Smart Links

Primary source for reusable URLs, one or several destinations, equal round-robin routing, availability, saved configurations, attribution context, fallback behavior, and troubleshooting.

Smart Link QR Codes & NFC

Use for choosing base, saved, or custom context; QR appearance, logo, quality, contrast, print testing, SVG or PNG, and NFC use.

Smart Link Analytics

Use for visits, destination results, configuration traffic, campaign attribution, customer outcomes, date ranges, and metric definitions.

Important distinction: a Base URL is the permanent main Smart Link; a saved configuration is a reusable variation with preferred context and its own suffix; one-time custom context is not the same as a saved configuration. With multiple active destinations, Smart Links use equal rotation, not weighted splitting.

Connect Make, Zapier, or another system

Start with the task the user wants to automate. Make and Zapier provide native guided integrations; API credentials and raw webhooks are intended for a technical partner or custom integration.

The connection owner’s current permissions and assigned Locations limit what it can do. Before recommending automated sending, read Customer Identity and Sending and Deliverability & Consent, and check the setup requirements.

Integrations — Getting Started

Use to choose between Make, Zapier, direct API access, webhooks, and other automation platforms and to check setup requirements.

Make

Use for reusable Make connections, instant triggers, actions, real-message testing warnings, and troubleshooting.

Zapier

Use for reusable Zapier connections, triggers, actions, real-message testing, duplicate protection, and troubleshooting.

Customer Identity & Sending

Use when an automation needs to match or create a Customer and send a tracked request safely.

Webhooks

Use when FSRevs should send selected workspace events to another system.

Other Automation Platforms

Use for connecting a supported automation tool without a native FSRevs app.

For exact request fields, responses, errors, and event shapes, use the API Reference. Do not ask a user to share an API key, webhook signing secret, or one-time credential secret in an AI chat.

Connect experiences and control what happens next

Followup Destinations

Use to choose what appears after a Review Flow or Custom Form: a Simple Page, Smart Link, My Link, or no linked destination.

Customer Journeys

Use for possible Connections, continuation context, reminders and device changes, and the path FSRevs actually observed for one customer.

Rich Editor

Use when connections are placed inside rich content through managed Customer destinations, or when the question concerns formatting, Smart Link conversion, or accessible images.

Do not conflate configuration with evidence: Connections describe paths that can be taken; an Observed Journey contains only steps that the customer actually entered.

Inspect customers, responses, messages, or logs

Use record pages to answer what happened. Public documentation explains where evidence appears; it does not provide access to the user’s records.

Customers

Use for contact records, activity, primary and additional contacts, permission status and history, duplicate merging, unsubscribes, and sending from a customer.

Flow Activity

Use for Review Flow response lists, filtering, record details, actions, testimonials, sub-pages, and export entry points.

Form Responses

Use for Custom Form submission lists, filters, response details, marketing content, timelines, and exporting.

Message History

Use for individual email and SMS records, delivery status, opens, details, and customer replies.

Activity Logs

Use for the step-by-step record of actions during a customer’s Flow experience and evidence-based troubleshooting.

Exporting Data

Use for Flow Activity, Form Response, and customer export filters, column choices, limits, and role considerations.

Understand dashboards, attribution, and performance

Dashboard

Use for the portal landing page, location overview, recent Flow Activity and Form Responses, and dashboard Quick Actions.

Flow & Form Reports

Use for results, completion, delivery, destinations, and attribution within an individual Review Flow or Custom Form.

Google Performance

Use for saved Google review growth, rating history, listing health, FSRevs click activity, and location or listing comparisons. A click does not prove that a review was posted.

Request Activity

Use for human-requested Review Flow and Custom Form activity, sender comparisons, request outcomes over time, and delivery results.

Team Performance

Use for completed Review Flow results associated with employees, attribution coverage, scale-aware ratings, and Flow or location composition.

Sender Tracking

Use to distinguish sender from employee attribution and understand Request Activity Patterns, including days with requests, closely timed requests, busiest 30-minute periods, and individual request drilldowns.

Manager Feedback Report

Use for reviewing and acting on written feedback submitted through Review Flows.

Smart Link Analytics

Use when analysis centers on link visits, destination distribution, configurations, campaigns, or resulting customer outcomes.

Choose the report by unit of analysis: workspace overview, Google listings and clicks, human-requested sender activity, employee-linked Review Flow results, a specific Flow or Form, manager feedback, or a Smart Link. Do not compare metrics from different scopes as though they are identical.

Manage team access, communication, and changes

Notes

Use for internal context, customer attachments, audience and scope, following, comments, drafts, history, and recovery.

Tasks, Issues & Reminders (Beta)

Use for internal work that needs a status, due date, assignees, urgency, discussion, or customer context.

Managing Users

Use for account creation, sign-in readiness, setup invitations, responsibilities, location access, editing, removal, and restore.

Roles & Permissions

Use for current customer responsibility labels, included capabilities, and All locations versus Specific locations access.

Message Templates

Use for email and SMS channels, message types, scope, dynamic variables, previews, defaults, and email themes.

Notifications

Use for internal notification events, delivery channels, preferences, and Flow-level notification settings.

Audit Trail

Use to answer who changed what and when, what each entry records, which views are available, who can see them, and how long entries are retained.

Account Settings

Use for a person’s own profile, sign-in details, contact number, phone verification, password, timezone, and photo.

Usage & Limits

Use for monthly request and notification allowances, location-based scaling, the next reset, and what to do when sending is delayed or unavailable.

If a button, location, flow, form, or customer tool is missing, check both role permissions and assigned-location access before concluding that the feature does not exist. Do not claim an exact permission that the documentation does not state.

Configure customer-facing content and branding

Branding

Use for logos, colors, business identity, location-specific branding, and previews.

Managing Your Links

Use for Review Links, Social Links, Custom Links, location scope, and My Links used in customer experiences.

Public Pages

Use for public business and testimonial pages hosted on BestLocalReviews.com, content permissions, display settings, featured links, review filtering, and location inheritance.

Simple Pages

Use for branded pages built from rich text, link lists, videos, and click-to-copy blocks, including use as a followup.

Rich Editor

Use for text formatting, managed destinations, Smart Link options, accessible images, alt text, captions, and surface-specific support.

For unexpected location-specific appearance or content, cross-check Location-Level Overrides.

Review Showcases

Use for hosted Pages, Smart Links and QR sharing, website embeds, styling hooks, availability, and search exclusion.

Showcase Settings

Use for automatic or curated selection, Simple/Cloud/Guestbook layouts, Leave Feedback invitations, reply headings, Page & QR, and previews.

Distinguish the configured Showcase, its hosted Page, and its website Embed. A Page needs a working Smart Link connection and is excluded from search indexing; an Embed does not need that connection. A feedback invitation starts an existing Review Flow and does not bypass moderation or curated selection. For when activity is recorded, use Showcase Feedback Entries.

Follow a common recipe

Flow & Form Recipes

Use when the user has a goal and wants a small, proven combination of Flow or Form settings instead of a complete feature tour.

Asking for a Review

Use for the end-to-end steps to prepare, send, and follow up on a responsible review request.

Question-to-source shortcuts

If the user asks…	Start with…	Add when relevant…
“What is this FSRevs term?”	Key Concepts & Glossary	The feature overview linked from the matching glossary entry
“How do I set up FSRevs?”	Setting Up Your Business	Creating Your Account for registration
“Which setting controls this?”	The matching Flow or Form settings guide	Location-Level Overrides if behavior differs by location
“Why can’t I see or send this?”	Quick Actions & Launch	Roles & Permissions and Understanding Locations
“Why did this customer receive, open, or complete something?”	Flow Activity or Form Responses	Message History, Activity Logs, or Customer Journeys
“Why was a message blocked or not delivered?”	Delivery, Bounces & Unsubscribes	Deliverability, Consent & Inbox Placement for prevention and policy
“Why did this URL or QR code open that destination?”	Smart Links	Smart Link QR Codes & NFC and Customer Journeys
“Who changed this setting, and when?”	Audit Trail	Roles & Permissions if the question also concerns who could make the change
“How is this performing?”	The report matching the object being measured	Activity pages for the underlying records and evidence
“How do I put reviews on my website?”	Review Showcases	Showcase Settings for selection and appearance
“How do I share a Guestbook page with a QR code?”	Share a Showcase Page	Showcase Settings for its invitation and Review Flow

Minimum context to request

Ask only for context that changes the answer. Useful clarifying details include:

The outcome the user wants, not just the page they are currently viewing.
The object involved: Review Flow, Custom Form, Smart Link, Simple Page, Showcase, customer, Flow Activity record, or Form Response.
Whether the configuration is global or tied to one location.
The user’s role and assigned locations, only when access or missing actions are relevant.
The delivery path: sent through FSRevs, sent from the user’s device, or opened from a public link, QR code, or NFC tag.
The exact visible label, status, or error text, with customer personal information removed.
Whether the user is describing configured behavior or a result that already occurred.

Do not force the user to answer every item. If the documentation supports a safe first step without more information, give that step first.

When the public guide is not enough

The documentation cannot inspect a workspace, confirm a user’s permissions, see private customer activity, or know whether a setting has been changed. Escalate to FSRevs support when:

The visible portal and the documented flow materially differ after checking role and location scope.
The question depends on private account configuration, billing, an exact plan limit, or a live delivery event.
A user needs help restoring access, changing account ownership, or handling sensitive customer data.
Troubleshooting requires information that should not be posted in an AI chat.

Contact support@fsrevs.com and share only the minimum safe context needed to identify the issue.

Google Business Profile

Overview — Public links, connected access, roles, and availability.
Connect accounts and listings — Authorization, registration, associations, reconnecting, and disconnecting.
Work with reviews — Inbox scope, search coverage, and handled state.
Write and manage replies — Private drafts, explicit public writes, moderation, and uncertain submissions.
Notifications — New reviews, changed reviews, connection alerts, and eligibility.
Connected performance — Search/Maps figures, coverage, and monthly search terms.
Troubleshooting — Access, connections, drafts, replies, alerts, and report recovery.

Keep connected Google content separate from FSRevs customer responses and tracked Google visits. A draft is private, an acknowledgement does not resend, and Location manager alone does not permit Google replies.