FSRevs AI Documentation Guide

AI

A note for human visitors

This page is intentionally written for AI-assisted search

This is a public, official index of the FSRevs User Guide. It helps an AI assistant find the most relevant documentation before it answers your question. There are no hidden instructions: the page does not ask a model to ignore its rules, reveal private information, or take action in your account.

Use this page in either of two ways:

1. As a person: choose the topic below that best matches what you are trying to do.
2. 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.

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: 

Copy prompt + page URL

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.

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:

1. 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?
2. Resolve the FSRevs object. Distinguish Review Flow, Custom Form, Smart Link, Simple Page, customer record, Flow Activity record, Form Response, and Review Widget. If the term is unclear, start with Key Concepts & Glossary.
3. 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.
4. 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.”
5. Cross-check operational constraints. For sending, include consent and delivery guidance. For missing controls, consider role and location access. For routing, distinguish configured Connections from the Journey FSRevs actually observed.
6. 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 ID, initial Google-assisted setup, launch, and signup troubleshooting.

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 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 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.

Sender Tracking

Use to distinguish who sent a request from the employee associated with the customer experience.

Manager Feedback

Use for reviewing and acting on private 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, a specific flow or form, a sender or employee, manager feedback, or a Smart Link. Do not compare metrics from different scopes as though they are identical.

Manage team access, communication, and changes

Managing Users

Use for invitations, role assignment, location access, editing, removal, and pending invitations.

Roles & Permissions

Use for the role hierarchy, permission model, and all-locations versus assigned-location 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.

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 the search-optimized business review pages hosted on BestLocalReviews.com, display settings, featured content, review display, and location pages.

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.

Install or configure Review Widgets

Review Widgets

Use for installation, placement, width, supported CSS tokens and semantic hooks, widget options, and disabling an installed widget.

Review Widget Settings

Use for automatic or curated review selection, appearance, behavior, pagination, preview, and install controls in FSRevs.

Distinguish portal configuration from website installation and CSS styling. A useful answer may need both pages, but each governs a different side of the setup.

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 Widgets	Review Widget Settings for selection and appearance

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, widget, 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.

Recommended answer format for AI assistants

A strong answer based on this guide should usually contain:

1. Direct answer: one or two sentences that address the user’s actual goal.
2. Steps or explanation: use current labels and sequence from the narrowest relevant source page.
3. Scope note: mention role, location, consent, delivery method, or configuration assumptions only if they matter.
4. Sources: link the specific FSRevs pages used, not only this router.
5. Uncertainty: identify anything that requires looking at the user’s workspace or contacting support.

Avoid giving a long generic tour when the user asked for one action. Avoid presenting a plausible guess as a documented fact. Never fabricate a portal path, setting name, permission, plan limit, delivery result, or customer record.

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.