# Rectify Help Center --- # Find your way around Rectify Collection: Getting started URL: https://app.rectify.so/rectify/help/a/1-find-your-way-around-rectify A quick tour of projects, the sidebar, search, Quanta and settings, so you know where everything lives. Rectify has two levels. Your **organization** is your company or team: it holds your members, your plan and your projects. A **project** is one product or site, with its own portal, widget, monitors and inbox. [Key terms in Rectify](/rectify/help/a/8-key-terms) explains the other words you'll meet. ## Open a project When you sign in, **Projects** lists every project in your organization. Select one to open it. Every project opens on **Quanta**, your AI teammate. ## The sidebar Everything in a project lives in the sidebar on the left. Select a group to open it. | **Group** | **What's inside** | | --- | --- | | **Set up** | Your setup checklist. Owners and Admins see it until setup is finished and your script is live. | | **Quanta** | Your AI teammate and the project's home page. | | **Inbox** | **Feedback**, **Session replays**, **Conversations**, **Channels** and **Knowledge base**. | | **Roadmap** | **Roadmaps**, **All posts**, **Review queue** and **Changelog**. | | **Customers** | **Contacts**, **Activity**, **Analytics**, **Heatmaps**, **Messaging** and **Surveys**. | | **Publish** | **Portal**, **Wiki**, **Widget** and **Help Center**. | | **Monitoring** | **Monitors**, **Incidents**, **Alerting** and **CodeScan**. | | **Project settings** | **Integrations**, **Workflows**, **Automation**, **Email notifications**, **MCP server**, **Chrome extension**, **Extension sessions** and **Snippets**. | | **Organization settings** | **General**, **Members**, **Domain**, **Billing** and **AI providers**. These apply to every project. | ## Get around faster 1. **Switch project or organization:** select the project name at the top of the sidebar. Search, pick another project, or select **All projects**. **New organization** and **All organizations** are at the bottom of the list. 2. **Search or jump to:** press ⌘K on a Mac or Ctrl K on Windows, then type the name of a page. 3. **Ask Quanta:** press ⌘J on a Mac or Ctrl J on Windows to ask Quanta from any project page. 4. **Notifications:** the bell shows your alerts. Select **Mark all read**, or the gear to change which alerts you get. 5. **Your account:** select your name at the bottom of the sidebar for **Profile**, **Rewards**, **Notifications** and **Logout**. ![1 Switch project. 2 Search or jump to. 3 Ask Quanta. 4 Notifications. 5 Your account.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106002072-01-shell.png) The project switcher also shows your other organizations, so you can move between them without signing out. ![The project switcher, with All projects and your organizations.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106003827-02-switcher.png) ## What to read next - [Set up your first project with the setup wizard](/rectify/help/a/3-set-up-your-first-project) - [Meet Quanta, your AI teammate](/rectify/help/a/7-meet-quanta) - [Invite your team](/rectify/help/a/6-invite-your-team) --- # Create your account and organization Collection: Getting started URL: https://app.rectify.so/rectify/help/a/2-create-your-account-and-organization Sign up for Rectify, verify your email, then create your organization and your first project. It takes about two minutes. Your organization and your first project come straight after your account. ## Create your account 1. Go to [app.rectify.so/sign-up](https://app.rectify.so/sign-up). 2. Select **GitHub** or **Google** to sign up with that account. Or fill in your **First name**, **Last name**, **Email address** and a **Password** of at least 8 characters. 3. Select **Create account**. ![2 Sign up with GitHub or Google, or with your email. 3 Create account.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106007339-01-sign-up.png) 4. If you signed up with your email, enter the 6-digit code we sent you. It expires in 5 minutes. 5. Sign in with your email address and password. Signing up with GitHub or Google skips the code and takes you straight to your organization. ## Create your organization Your organization holds your team, your plan and every project. You become its **Owner**, and it starts on the free **Idea** plan. 1. Enter your **Organization name**: your company or team, from 2 to 50 characters. You can rename it later. 2. To add a logo, select **Upload** and pick a PNG or JPG up to 5 MB. This is optional. 3. Select **Create organization**. ![1 Organization name. 2 Logo. 3 Create organization.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106009386-02-organization.png) ## Create your first project A project is one product or site, with its own portal, widget, monitors and inbox. Most teams make one per product. 1. Check the **Name**. It starts as your organization's name, and it shows on your portal, your widget and every email. 2. Add your **Website** if you have one. Quanta reads it in the next step to set up your brand, an uptime monitor and help content. You can add it later. 3. Select **Create project**. The setup wizard opens next. [Set up your first project with the setup wizard](/rectify/help/a/3-set-up-your-first-project) walks you through it. ## Joining a team instead? If a teammate invited you, you don't need your own organization. Open the link in the invitation email and select **Accept invitation**. No account yet? Sign up first, with the same email address the invitation was sent to. [Invite your team](/rectify/help/a/6-invite-your-team) explains what happens next. ### It says "An account already uses this email" That email address already has a Rectify account. Select **Sign in instead**. If you've forgotten your password, select **Forgot password?** on the sign-in page. ### The code doesn't work A code works for 5 minutes and allows 3 tries. Select **Send a new code**, then use the code in the newest email from us. You can ask for a new code once a minute. ### It says "An organization with this name already exists" Organization names are unique across Rectify. Add your team or city to the name to tell them apart, for example "Acme Inc Berlin". --- # Set up your first project with the setup wizard Collection: Getting started URL: https://app.rectify.so/rectify/help/a/3-set-up-your-first-project Five short steps to brand your project, switch on what you need, bring in your team and add Rectify to your site. > **Note:** **Before you start.** Owners and Admins can run setup. It takes about five minutes. Your choices are saved as you go, and **Skip for now** at the top leaves the rest for later. The wizard opens when you create a project. To come back to it later, open **Set up** in the sidebar and select **Let's GO!** or **Continue setup**. ## Step 1: Your site 1. Enter your website under **Your website**. 2. Select **Read my site**. Quanta reads your public pages and picks up your logo, your brand colour and your help pages. 3. Check the logo and the **Brand colour**, and change them if you like. 4. Select **Continue**. ![1 Your website. 2 Read my site.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106012146-01-site.png) No website yet? Upload a logo or leave it out (the first letter of your project stands in), pick a colour, and select **Continue**. ## Step 2: What you need Pick what this project should do. Each one sets up its part of Rectify with sensible defaults, and you can switch any of them on or off later. | **Pick** | **What it sets up** | | --- | --- | | **Support customers** | A Support tab on the widget. Quanta answers from your site and hands over to you. Needs your website. | | **Collect feedback** | Bug and idea forms, a Feature Requests board and a public roadmap. | | **Watch uptime** | Your site checked around the clock, with email alerts to you. Needs your website. | | **Understand usage** | Analytics, contacts and heatmaps, from the same script. | | **Publish updates** | A changelog on the portal and a Changelog tab on the widget. | | **Help articles** | The help pages on your site, imported as drafts. A Help tab on the widget. Needs your website. | All six start switched on. Turn off what you don't need, then select **Set these up**. ![The six picks in What you need.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106014053-02-goals.png) If Quanta found pages on your site, you can also choose the pages it learns from and the help pages to import. Imported help pages stay drafts until you publish them. How many pages Quanta reads depends on your plan: | **Plan** | **Pages Quanta reads** | | --- | --- | | Idea | 50 | | Build | 150 | | Launch | 300 | | Accelerate and Enterprise | 500 | Your widget and portal are set up whatever you pick. Nothing reaches your customers until the script is on your site. ## Step 3: Make it yours Choose your widget's **Greeting** (up to 120 characters), its **Position** (**Left**, **Right** or **Side**), the **Launcher** style (**Icon**, **Pill** or **Tab**) and the **Corners** (**Sharp**, **Soft** or **Round**). The preview on the right shows your site with the widget on it. Select **Preview portal** to see your public portal, then select **Continue**. You can change all of this later under **Publish**, **Widget**. ## Step 4: Team, code and AI Everything here is optional. Select **Continue** when you're done, or **Skip these**. - **Invite your team:** enter a teammate's email, pick **Admin** or **Member**, and send. You can invite up to 10 people at once. On the free Idea plan, sending invites starts a free 14-day Build trial with three seats, and no card is needed. - **Connect GitHub:** select **Connect GitHub**, approve Rectify on GitHub, then pick a repository and select **Use this repository**. - **Connect your AI provider:** pick a provider, paste your API key and choose a **Model**. Then select **Connect** with the provider's name, for example **Connect Claude**. Without one, Quanta runs on the Rectify credits included with paid plans. ## Step 5: Install Pick how to add the Rectify script to your site: - **Let your AI do it:** copy a prompt for your AI coding tool. - **Paste it yourself:** copy the snippet for your framework. - **Send to a developer:** email the install steps to a teammate. The page ticks itself the moment the script loads on your site. Select **Finish setup** to see what's left. ![The ways to add the script to your site.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106015711-03-install.png) [Install the Rectify widget on your site](/rectify/help/a/5-install-the-rectify-widget) has the snippet for each framework, and [Finish the Set up checklist](/rectify/help/a/4-finish-the-set-up-checklist) covers what comes after setup. ### It says "We couldn't read" my site Quanta reads public pages only. Check the address opens in a private browser window without a sign-in, then select **Read again**. You can also skip the read, add your logo and colour yourself, and continue. ### It says "That site was read a lot just now" A project can read its site 10 times in 10 minutes. Wait a few minutes, then try again. --- # Finish the Set up checklist Collection: Getting started URL: https://app.rectify.so/rectify/help/a/4-finish-the-set-up-checklist See what's left to set up in your project, finish each item, and get your script live. > **Note:** **Before you start.** The checklist is for Owners and Admins. Members can open it, but they can't change anything there. After the setup wizard, **Set up** at the top of the sidebar shows what's left. The page counts the things left to do and sorts them into **Needs you**, **Working** and **Ready**. ![Set up in the sidebar, and what's left to do.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106018647-01-checklist.png) ## What's on the list | **Item** | **When it's done** | | --- | --- | | **Install the script** | When your site sends its first events. It needs **Understand usage** switched on in setup. | | **Invite your team** | When you've invited someone, or your organization has more than one member. | | **Connect GitHub** | When the Rectify GitHub app is installed for a repository. | | Anything you skipped | It shows the reason, for example "Add your website to watch it". | Below the list, each part of your project shows how it's doing: **Brand**, **Widget**, **Portal**, **Uptime monitor**, **Help Center**, **Support answers** and **Analytics**. Each one reads **Ready**, **Working**, **Didn't finish** or **Waits for the script**. ## Finish an item 1. Open **Set up** in the sidebar. 2. Select an item to open it. 3. Follow the steps inside. For example, **Install the script** has the snippet and **Invite your team** has the invite form. For something you skipped, select **Open this step** to go back to that step of the wizard. ## If reading your site stopped If **Quanta couldn't read your site** shows at the top, select **Try again**. Everything else is already set up, so trying again only reads your pages. ## When Set up goes away **Set up** leaves the sidebar once setup is finished and your script is live. If your site sends no events for 24 hours, the install item unticks and **Set up** comes back, so you know to check your script. ### The install item doesn't tick It ticks when events arrive from your site, so open a page on your site with the script on it and wait a minute. If you switched off **Understand usage**, it can't tick. [The widget doesn't show: what to check](/rectify/help/a/24-the-widget-does-not-show) helps you check the script. --- # Install the Rectify widget on your site Collection: Getting started URL: https://app.rectify.so/rectify/help/a/5-install-the-rectify-widget Add one script to your site to turn on the widget, analytics and contacts. > **Note:** **Before you start.** You need access to your site's code, or to the custom code settings of your site builder. One script powers the widget, analytics and contacts. It loads after your page, so it doesn't slow your site down. ## Add the script 1. In your project, open **Publish**, then **Widget**. ![1 Widget, under Publish in the sidebar.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106021215-01-open-widget.png) 2. On the right of the Widget page, select **Install**. ![2 Install, on the right of the Widget page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106023073-02-open-install.png) 3. Under **Add the script**, pick where your site is built. The line under the list tells you where the script goes. 4. Select **Copy**. ![3 Pick where your site is built. 4 Copy the script.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106026846-03-add-script.png) 5. Paste the script where that line says, then save and publish your site. > **Tip:** Copy the script from Rectify rather than from this article. The copy in Rectify already has your project ID filled in. ## Where the script goes The script is the same everywhere. Only where you paste it changes. | **Where your site is built** | **Where the script goes** | | --- | --- | | JavaScript | Paste it once, before the closing tag | | Next.js | Add it to app/layout.tsx so it loads on every page | | React | Run it once when the app mounts | | Vue | Run it once in your root component | | Nuxt | Add it as a client plugin in plugins/rectify.client.ts | | Angular | Run it in your root component's ngOnInit | | Svelte | Run it once in your root layout | | Tag Manager | Create a Custom HTML tag, trigger All Pages, paste this | | Webflow | Project settings, Custom code, Footer code, then publish | | WordPress | Theme footer.php before , or any header and footer plugin | | Shopify | Online store, Themes, Edit code, theme.liquid before | | Framer | Site settings, General, Custom code, End of body tag | ## What the script looks like Here is the script for each platform. Rectify fills in your own project ID where you see `YOUR_PROJECT_ID`. **JavaScript** ```html ``` **Next.js** ```jsx import Script from 'next/script'; ``` **React** ```javascript useEffect(() => { const js = document.createElement('script'); js.src = 'https://api.rectify.so/widget/widget.umd.js'; js.async = true; js.onload = () => { if (typeof window.Rectify === 'function') { window.RectifyInstance = new window.Rectify(); window.RectifyInstance.init('YOUR_PROJECT_ID'); } }; document.head.appendChild(js); }, []); ``` **Vue** ```javascript onMounted(() => { const js = document.createElement('script'); js.src = 'https://api.rectify.so/widget/widget.umd.js'; js.async = true; js.onload = () => { if (typeof window.Rectify === 'function') { window.RectifyInstance = new window.Rectify(); window.RectifyInstance.init('YOUR_PROJECT_ID'); } }; document.head.appendChild(js); }); ``` **Nuxt** ```javascript export default defineNuxtPlugin(() => { const js = document.createElement('script'); js.src = 'https://api.rectify.so/widget/widget.umd.js'; js.async = true; js.onload = () => { if (typeof window.Rectify === 'function') { window.RectifyInstance = new window.Rectify(); window.RectifyInstance.init('YOUR_PROJECT_ID'); } }; document.head.appendChild(js); }); ``` **Angular** ```typescript ngOnInit() { const js = document.createElement('script'); js.src = 'https://api.rectify.so/widget/widget.umd.js'; js.async = true; js.onload = () => { if (typeof (window as any).Rectify === 'function') { (window as any).RectifyInstance = new (window as any).Rectify(); (window as any).RectifyInstance.init('YOUR_PROJECT_ID'); } }; document.head.appendChild(js); } ``` **Svelte** ```javascript onMount(() => { const js = document.createElement('script'); js.src = 'https://api.rectify.so/widget/widget.umd.js'; js.async = true; js.onload = () => { if (typeof window.Rectify === 'function') { window.RectifyInstance = new window.Rectify(); window.RectifyInstance.init('YOUR_PROJECT_ID'); } }; document.head.appendChild(js); }); ``` **Tag Manager** ```html ``` **Webflow** ```html ``` **WordPress** ```html ``` **Shopify** ```html ``` **Framer** ```html ``` ## Check it worked 1. Open your site in a new tab and refresh it. The widget's launcher appears on the page. 2. In Rectify, **Widget on your site** at the top of **Install** shows **Live**. When it shows **Paused**, the widget is hidden everywhere, and you don't need to change your code. If you're setting up a new project, the **Install** step in the setup ticks itself off the moment the script loads. ## Other ways to install When you set up a new project, the **Install** step offers two more ways in: - **Let your AI do it:** copy the prompt, paste it into your AI coding tool and deploy. - **Send to a developer:** email the script to the person who looks after your site. ## Troubleshooting ### The widget doesn't show on my site - Check that **Widget on your site** shows **Live** under **Install**. - Make sure the script is on every page. In a site builder, add it to the site-wide custom code, not to a single page. - If your site builder has a **Publish** button, publish again after you add the script. - Copy the script again from **Install** and paste it fresh, in case part of it was cut off. ### Where do I find my project ID? It's in the script you copy from **Install**, on the line that starts with `projectId`. The **Install** section also shows how to identify signed-in visitors and how to open the widget from your own buttons. --- # Invite your team Collection: Getting started URL: https://app.rectify.so/rectify/help/a/6-invite-your-team Add teammates to your organization and choose which projects each person can open. > **Note:** **Before you start.** You need to be an Owner or Admin. Every member and every pending invitation takes a seat, so you need a plan with a free seat. ## Send an invitation 1. Open **Organization settings**, then **Members**. 2. Select **Invite Member**. ![2 Invite Member, at the top of the Members page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106029524-01-invite-member.png) 3. Enter their **Email Address**. 4. Pick a **Role**. Admins have full access to all projects and organization settings. Members can only open the projects you assign to them. 5. For a Member, choose at least one project under **Project Access**. 6. Select **Send Invitation**. ![3 Email Address. 4 Role. 5 Project Access. 6 Send Invitation.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106031140-02-invite-dialog.png) Rectify emails them a link to join, and the invitation waits under the **Invitations** tab until they accept it. ## What your teammate does 1. Open the link in the invitation email. 2. Sign in, or sign up, with the same email address you invited. 3. Select **Accept invitation**. Rectify opens your organization's projects. > **Tip:** The invitation only works for the exact address you invited. If your teammate wants to use another address, invite that one instead. ## Resend or cancel an invitation Invitations last 7 days. To send a fresh link, open the **Invitations** tab, open the menu on the invitation and select **Resend**. The new email replaces the old link, which stops working. To withdraw an invitation, select **Cancel**. ![Resend and Cancel, in the menu of a pending invitation.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106032972-03-resend-cancel.png) ## Seats on each plan | **Plan** | **Seats** | | --- | --- | | Idea (free) | 1 | | Build | 3 | | Launch | 10 | | Accelerate | 25 | | Enterprise | Unlimited | The line under **Members** shows how many seats you've used, counting pending invitations. On the free Idea plan, your one seat is yours, so **Invite Member** is turned off. You can upgrade, or use the **Invite your team** step in your project's setup: it starts a free 14-day Build trial with three seats, and no card is needed. ## Troubleshooting ### The Invite Member button is greyed out or missing If it's greyed out, every seat on your plan is taken, or you're on the free Idea plan. Upgrade your plan, or remove a member or cancel an invitation to free a seat. If you don't see the button at all, you're a Member: ask an Owner or Admin to send the invitation. ### It says "Invitation already sent to this email" That person already has a pending invitation. Open the **Invitations** tab and select **Resend** instead. ### It says "User is already a member" They're already in your organization. To change what they can open, open the menu on their row and select **Edit Member**. ### My teammate sees "Invalid or expired invitation" The link is more than 7 days old, the invitation was cancelled, or it was resent and the old link was replaced. Resend the invitation and ask them to use the newest email. --- # Meet Quanta, your AI teammate Collection: Getting started URL: https://app.rectify.so/rectify/help/a/7-meet-quanta What Quanta can do for your project, where to find it, and how you approve the changes it makes. Quanta is the AI teammate built into every project. It knows your feedback, roadmap, customers and monitors, and it can: - answer questions about your project, like "What changed this week?" or "Who might churn?" - make changes for you, like adding a roadmap card or drafting a changelog entry, once you confirm them - answer your customers in the widget, from your Help Center and your Knowledge base - check your project on a schedule and post a short report. ## Open Quanta Every project opens on Quanta. You can also select **Quanta** at the top of the sidebar, or **Ask Quanta** in the top bar of any project page (⌘J on a Mac, Ctrl J on Windows). The page starts with a short briefing: what needs you today and your latest numbers. Type in the box at the bottom to ask anything, or pick a suggestion above it. ![1 Quanta in the sidebar. 2 Ask anything here.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106035525-01-home.png) **History** at the top lists your earlier chats, and **Usage** shows what Quanta has used. ## Approve what Quanta changes Quanta doesn't change anything until you say so. 1. Ask Quanta for a change, for example "Add a roadmap card for dark mode". 2. A card appears under Quanta's reply. It sums up the change and lists what will be saved. 3. Select **Confirm** to go ahead. To leave it, select **Cancel** instead. Nothing changes until you confirm. A card waits 30 minutes. After that, ask Quanta to prepare the change again. When Quanta asks you a question with a short form and you answer it, small follow-up changes go ahead without a card to confirm. Deleting, archiving, unpublishing, merging, sending and stopping always ask first. ## Get a report on a schedule On the Quanta page, the organization's Owner can select **Turn on reports** and choose how often Quanta checks, from every 10 minutes to every 24 hours. Quanta posts a short **Project Report** and alerts you if something breaks. Open it any time from **History**. ## Let Quanta answer your customers 1. Open **Publish**, then **Widget**, and select **Support**. 2. Under **Answered by**, pick who answers: - **Quanta first:** Quanta answers first and hands over to your team when it can't help. This is the default. - **Quanta only:** fully automated. Customers can't reach your team from the chat. - **Team only:** only your team answers. Quanta answers from your Help Center articles and your Knowledge base, so the more you publish, the better its answers get. ## What Quanta runs on Quanta runs on your own AI provider key, or on the Rectify credits that come with paid plans. Connect a key and set a monthly limit under **Organization settings**, **AI providers**. [Set a monthly spend limit on your AI keys](/rectify/help/a/16-set-a-spend-limit-on-your-ai-keys) explains how. ### It says "No AI provider is configured" Your organization has no AI key connected and no Rectify credits left. Ask an Owner or Admin to connect a provider under **Organization settings**, **AI providers**. ### It says "Action not found or expired" The card waited more than 30 minutes. Ask Quanta to prepare the change again. --- # Key terms in Rectify Collection: Getting started URL: https://app.rectify.so/rectify/help/a/8-key-terms What organization, project, portal, board, post and the other words you see in Rectify mean. The words you'll see most often in Rectify, in the order you'll meet them. | **Term** | **What it means** | | --- | --- | | **Organization** | Your account. It holds your projects, your team and your plan. Seats and projects are counted across the organization. | | **Project** | One product or site. Each project has its own portal, widget, monitors and inbox. | | **Owner, Admin, Member** | The three roles in an organization. Admins see every project; Members see the projects they're given. | | **Quanta** | Rectify's AI teammate. It answers questions about your project, takes actions you approve, and answers your customers in the widget. | | **Widget** | The script you add to your site. It gives your users feedback forms, support chat, your roadmap, changelog and help articles. | | **Feedback** | A bug report, idea, general feedback or testimonial sent from the widget. Bug reports can include a session replay. | | **Session replay** | A recording of what the user did before they sent a bug report. | | **Conversation** | A support chat with a customer, in your **Inbox**. | | **Portal** | Your public page for requests, your roadmap, your changelog and your status. | | **Board** | Where requests collect. Every project starts with a board called **Feature Requests**. | | **Post** | One request on a board. On the portal your users see posts as **Requests**. | | **Roadmap** | What you plan, are working on and have shipped, built from your posts. | | **Changelog entry** | An update about something you shipped. It's a draft, scheduled or published. | | **Help Center** | Your help articles, grouped into collections, on your portal and in the widget's Help tab. | | **Contact** | A person who uses your product, known from the widget, your forms or the Contacts API. | | **Segment** | A saved group of contacts that match the rules you set, used to target surveys, messages and help articles. | | **Monitor** | A check Rectify runs on your site, API, server or scheduled job to catch problems before your customers do. | --- # What Quanta can do for your team Collection: Quanta URL: https://app.rectify.so/rectify/help/a/34-what-quanta-can-do What Quanta can read and change in your project, where its answers come from, and how to use prompts, models, files and your GitHub repository. > **Note:** **Before you start.** Everyone who can open a project can chat with Quanta there. Quanta runs on your own AI provider key, or on the Rectify credits that come with paid plans. A few changes are for Owners and Admins only, listed below. [Meet Quanta, your AI teammate](/rectify/help/a/7-meet-quanta) shows where Quanta lives. This article covers everything it can do once you start asking. ## What Quanta can look at and change Quanta reads your project live every time you ask, so its answers use today's numbers. When you ask for a change, Quanta prepares it and waits for you to confirm. [Ask Quanta and approve its changes](/rectify/help/a/35-ask-quanta-and-approve-changes) explains how that works. | **Area** | **Ask about** | **Ask it to change** | | --- | --- | --- | | **Feedback** | Bugs, ideas and testimonials, one report in detail, this week's trends | Log new feedback; change status, type, priority or who it's assigned to; add a note | | **Roadmap and portal** | Boards, posts, statuses, tags, comments and the review queue | Add, edit, move or merge posts; manage boards, statuses and tags; reply to comments; approve or decline what's waiting for review | | **Changelog** | Entries, labels and subscribers | Write an entry or several drafts; publish, schedule or unpublish an entry | | **Wiki** | Your Wiki pages | Create, edit or archive a page | | **Monitoring** | Monitors, uptime and incidents | Add, pause, resume or remove a monitor; open, update or resolve an incident | | **Customers** | Contacts, companies and segments | Nothing. Quanta only reads these | | **Analytics** | Traffic, goals, alerts, heatmaps and where visitors struggle | Pause or resume an analytics alert | | **Support** | Conversations and how your support is doing | Resolve, reopen or archive a conversation | | **Help Center and Knowledge base** | Articles, content gaps, FAQs and snippets | Add an FAQ or a snippet | | **Messaging** | Surveys, popups, campaigns and email tests | Create, publish or pause a survey; turn a popup on or off; draft or send a campaign; start or stop an email test | | **Workflows and webhooks** | Workflows, failed runs and webhooks | Build a workflow; turn a workflow or webhook on or off; send a test event | | **Code** | Code scan results and files in your connected repository | Start a new code scan | | **Widget** | Your widget settings and install snippet, and the sites it runs on | Change colours, the launcher and which tabs show, and give a site or page its own launcher | Quanta can also make a PDF report of your feedback, code scans or monitoring, and keep a preference you ask it to remember for your next chats. Some changes only go through for Owners and Admins: publishing or changing changelog entries, changing portal settings, changing workflows or webhooks, sending campaigns, and starting or stopping email tests. Calling you on the phone is for the organization's Owner. ## Where Quanta's answers come from - **Your project's data:** feedback, roadmap, changelog, monitors, customers, analytics, support and the rest, read when you ask. - **Your Help Center and Knowledge base:** Quanta searches your articles and your FAQs, websites and documents when a question needs them. - **Your GitHub repository:** once you connect one, Quanta can read its files and start code scans. It reads the `main` branch and suggests changes, but never edits your code. - **The chat so far:** Quanta remembers what you said earlier in the same chat. ## Start from a ready-made prompt The Quanta page shows suggestions above the message box, like **What changed this week?** and **Who might churn?**. Select one and Quanta answers straight away. For more ideas: 1. Select **Prompts**. 2. Pick a topic: **Feedback**, **Code Scan**, **Monitor**, **Report**, **Roadmap** or **General**. 3. Select a prompt. It fills the message box, so you can edit it before you send. ![1 Prompts. 2 A topic. 3 A prompt to start from.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106182493-01-prompts.png) ## Choose the model The menu next to the microphone shows **Best** until you change it. - **Best** picks for you. Quanta uses the provider that has **Quanta Chat** under **Powers** in **Organization settings**, **AI providers**. If none has it, Quanta uses another key you've connected, and your Rectify credits come last. If a provider fails, the next one takes over. - **A named model** is used for your messages as long as its provider is connected. The menu lists the models of each provider you've connected. On Rectify credits, that's **deepseek-v4-flash**. ![1 Best picks for you. 2 A model you can choose.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106184792-02-model.png) Your choice lasts until you reload the page. ## Add files to a message 1. Open a chat and select the paperclip (**Attach files**). 2. Pick up to 3 files. Images can also be pasted into the message box. 3. Type your question about them and send. Quanta reads JPEG, PNG and WebP images and PDF files up to 10 MB each. Images and longer PDFs are read with Gemini, so they need a Gemini key under **AI providers**. ## Connect your GitHub repository Connect a repository so Quanta can read your code and start code scans. 1. Select **Connect GitHub** under the message box. 2. Select **Connect GitHub Account** and approve Rectify on GitHub. You come back to the same page. ![2 Connect GitHub Account.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106186429-03-github.png) 3. Select **Connected** under the message box. 4. Pick your repository under **Repository**. 5. Select **Save**. The button then shows your repository's name. Owners and Admins can remove the connection with **Disconnect** in the same window. ### It says "You can only upload a maximum of 3 files." A message takes up to 3 files. Remove one, or send the rest in your next message. ### It says "Invalid file type" or "File size is too large" Quanta reads JPEG, PNG and WebP images and PDF files, up to 10 MB each. Save other files as PDF, or shrink large images, and attach them again. ### It says "Analytics is not included in this plan" Analytics, goals and alerts start on the Build plan. [Compare plans and what each one includes](/rectify/help/a/13-compare-plans) lists what each plan has. ### A Repository list says "Failed to fetch repositories" Rectify lost access to your GitHub account. Select **Reconnect**, approve Rectify on GitHub again, then pick your repository. ## Read next - [Ask Quanta and approve its changes](/rectify/help/a/35-ask-quanta-and-approve-changes) - [Work with canvas panels and Expand](/rectify/help/a/36-canvas-panels-and-expand) - [Set a monthly spend limit on your AI keys](/rectify/help/a/16-set-a-spend-limit-on-your-ai-keys) --- # Ask Quanta and approve its changes Collection: Quanta URL: https://app.rectify.so/rectify/help/a/35-ask-quanta-and-approve-changes Start a chat, approve or skip the changes Quanta prepares, answer its questions, and find your chats again in History. > **Note:** **Before you start.** Everyone who can open a project can chat with Quanta and confirm changes there. A few changes, like publishing changelog entries or sending campaigns, only go through for Owners and Admins. [What Quanta can do for your team](/rectify/help/a/34-what-quanta-can-do) lists them. ## Start a chat 1. Open **Quanta** in the sidebar. 2. Type your question in the box at the bottom. 3. Press Enter to send. Shift+Enter adds a new line. Quanta names the chat after your first message. Select **New Chat** at the top of a chat to go back to the Quanta page and start another one. Chats you don't touch for a while are deleted. The line under the chat's name shows when, and every new message starts the clock again. | **Plan** | **A chat is kept for** | | --- | --- | | Idea | 1 month | | Build | 3 months | | Launch | 6 months | | Accelerate and Enterprise | 12 months | ## Approve a change Quanta never changes anything until you confirm it. 1. Ask Quanta for a change, for example "Log a bug: the checkout button does nothing on Safari. High priority." 2. Check the card under Quanta's reply. It sums up the change and lists what will be saved. A red warning tells you when a change can't be undone. 3. Select **Confirm**. ![2 The change and what will be saved. 3 Confirm.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794742140029-01-confirm.png) The card then reads **Done**. If the change doesn't go through, it reads **Failed** and a message tells you why. Not sure yet? Select **Cancel** and the card reads **Canceled**. Nothing is saved until you select **Confirm**. A few things to know: - A card waits 30 minutes. After that, ask Quanta to prepare the change again. - Only the person who asked can confirm a change. - Quanta prepares one change per reply. If you ask for two at once, confirm the first, then ask for the next. - A card that's still waiting goes away when you reload the page or leave the chat. Ask Quanta again to bring it back. ## Answer Quanta's questions When Quanta needs details for a change, it shows a short form above the message box instead of guessing. 1. Pick an answer, or type your own under the choices. 2. Select **Continue** to go to the next question. 3. On the last question, select **Send**. ![1 Pick an answer or type your own. 2 Continue.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106190852-02-question-form.png) After you answer, small follow-up changes go ahead without a card to confirm. Deleting, archiving, declining, unpublishing, resending, merging, sending, stopping and picking a winner still ask you first. To skip the questions, close the form. The reply is then marked **Canceled**. ## Copy or retry a reply Under each reply from Quanta: - **Copy** copies the reply's text. - **Retry** asks again with the model you've picked in the message box, and replaces the reply. While Quanta is replying, the send button shows a spinner and you can send your next message once it's done. Quanta can make mistakes, so check anything important before you act on it. ## Find, star, rename or delete a chat 1. Open any chat and select **History** at the top. 2. Point at a chat and open the menu next to it. 3. Select **Star**, **Rename** or **Delete**. A chat from a feedback report, a session replay, a support chat or an extension session has **Remove from history** instead of **Delete**. ![2 A chat from a feedback report. 3 Remove from history.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794742142567-03-history.png) History lists your chats with Quanta from every place you use it: the Quanta page, feedback reports, session replays, support chats, analytics and extension sessions. A chat that started somewhere else shows where under its name, like **Feedback** or **Support chat**. Selecting it takes you back to where it started, with Quanta's chat open. To see one place only, pick it at the top of History, for example **Feedback** or **Replays**. **All** shows everything again. These choices appear once you've chatted with Quanta in more than one place. History shows **Project Report** first, then **Starred** and **Recents**. Older chats load as you scroll. History only lists your own chats, plus the Project Report, which everyone on the project can open. [Heartbeat: scheduled check-ins and urgent alerts](/rectify/help/a/38-heartbeat-check-ins-and-alerts) explains the Project Report. Deleting a chat can't be undone. **Remove from history** only takes a chat off your list. The chat stays with its feedback report, replay, support chat or extension session, and it's back in History the next time you chat with Quanta there. ### It says "Action not found or expired. Ask Quanta to prepare it again." The card waited more than 30 minutes. Ask Quanta for the change again. ### It says "This action does not belong to you." Only the person who asked for a change can confirm it. Ask Quanta for the change in your own chat. ### It says "Only owners and admins can publish or change changelog entries." That change needs an Owner or Admin. Ask one of them to confirm it from their own chat. ### It says "This chat is no longer available" The feedback report, support chat, extension session or analytics chat it came from was deleted, so History takes the chat off your list. ### Quanta stopped and says it reached its step limit Quanta takes up to 50 steps for one reply. What it changed before stopping is saved. Reply "continue" and it picks up where it left off. ## Read next - [Work with canvas panels and Expand](/rectify/help/a/36-canvas-panels-and-expand) - [What Quanta can do for your team](/rectify/help/a/34-what-quanta-can-do) - [Heartbeat: scheduled check-ins and urgent alerts](/rectify/help/a/38-heartbeat-check-ins-and-alerts) --- # Work with canvas panels and Expand Collection: Quanta URL: https://app.rectify.so/rectify/help/a/36-canvas-panels-and-expand Open and close the panels Quanta shows next to the chat, expand a small card into the full view, and share a chat with a link. > **Note:** **Before you start.** Canvas panels open in any Quanta chat, for everyone who can open the project. Only the person who started a chat can share it. When you ask Quanta to show something, like your feedback, your roadmap or your monitors, it opens the full view in a panel next to the chat. That panel is a canvas. For quick answers, Quanta shows a small card inside the chat instead. ## Open and close a canvas A canvas opens by itself when Quanta's reply is ready. Under the reply, a card with the canvas's name lets you bring it back. 1. Select the card under a reply, for example **Project Dashboard**, to open the canvas. The card says **Open canvas** or **Close canvas**. 2. Close the canvas with the **X** at its top right, or select the card again. ![1 The card under the reply. 2 Close the canvas.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106195320-01-canvas.png) To make the canvas wider or narrower, drag its left edge. On a phone, the canvas fills the screen; tap outside it to close it. Canvases cover most of Rectify, including: - **Feedback**, **Roadmaps**, **Review queue**, **Portal settings** and **Changelogs** - **Analytics**, **Goals**, **Analytics alerts**, **Heatmaps** and **Session Replays** - **Support**, **Help Center** and your Wiki **Documents** - **Contacts**, **Companies** and **Segments** - **Monitoring** and **Code Scan** - **Surveys**, **Popups**, **Campaigns**, **Workflows** and **Webhooks** - **Widget Configuration**, **Project Dashboard** and **Quanta Cost Overview** ## Act from a canvas Many canvases have buttons, like **Change status** on a feedback report or **Resolve** on a support conversation. Selecting one sends the request to Quanta in the chat, so the change still waits for you to confirm it. [Ask Quanta and approve its changes](/rectify/help/a/35-ask-quanta-and-approve-changes) explains how. Two canvases save straight away when you use their own buttons: the changelog editor, with **Publish** and **Save draft**, and the workflow builder. ## Expand a card into the full view 1. Find a card in Quanta's reply that has **Expand** under it. 2. Select **Expand**. The full view opens as a canvas, with fresh numbers. ![1 Expand opens the full view.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106198387-02-expand.png) Expand works for the project dashboard, the feedback, support and monitoring overviews, analytics, code scans and Quanta's own cost overview. To get a card, ask for a quick summary, for example "Give me the key project numbers in the chat". ## Come back to a canvas later When you open an older chat, the card under a reply reopens the canvas as it looked when Quanta showed it. To see today's numbers, ask again or use **Expand**. Saved canvases are kept as long as the chat is. These aren't saved, so ask Quanta again to bring them back: an email preview, the changelog editor and the workflow builder. ## Share a chat Sharing makes the whole chat readable by anyone with its link. 1. Open the chat and select **Share** at the top. 2. Turn on **Make Public**. 3. Copy the link under **Share Link**. ![2 Make Public creates the link.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106199941-03-share.png) People with the link see the messages, but not the canvases, and they can't reply. To stop sharing, turn **Make Public** off again. ### It says "This view couldn't be shown" Something in that canvas failed to load. Ask Quanta again, or open the same page in the sidebar. ### It says "This view has expired. Ask Quanta to show it again." The saved copy of that canvas is gone. Ask Quanta for the view again. ### Someone opens my shared link and sees "Chat not found" The chat is private again, or it was deleted. Open **Share** and turn on **Make Public**, then send the link again. ## Read next - [Ask Quanta and approve its changes](/rectify/help/a/35-ask-quanta-and-approve-changes) - [What Quanta can do for your team](/rectify/help/a/34-what-quanta-can-do) --- # Talk to Quanta with your voice Collection: Quanta URL: https://app.rectify.so/rectify/help/a/37-talk-to-quanta-with-your-voice Dictate a message, hold a spoken conversation with Quanta, choose its voice and language, and set up phone calls through Twilio. > **Note:** **Before you start.** Everyone who can open a project can dictate and use voice chat there. Only the organization's Owner can change Quanta's voice settings, set up phone alerts and place a test call. Dictation on the free Idea plan is limited to 30 minutes a month; paid plans have no limit. There are two buttons next to the message box: - **The microphone** types what you say into the message box, so you can check it before you send. - **The waveform** starts a spoken conversation. Quanta listens, answers out loud and keeps both sides in the chat. ![1 Dictate a message. 2 Start a voice chat.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106202392-01-composer.png) ## Dictate a message 1. Select the microphone next to the message box. 2. Allow your browser to use the microphone, if it asks. 3. Speak. A timer shows how long you've been recording. 4. Select the stop button when you're done. 5. Check the text in the message box, then send it. You can also start and stop with the keyboard when you're not typing in the box: hold Space while you speak, or press Ctrl+M (⌘M on a Mac) to start and again to stop. A recording can be up to a minute long. The timer turns orange in the last ten seconds, so stop before it reaches 1:00. To throw a recording away, select the **X** next to the timer. Dictation works out which language you're speaking. ## Have a voice chat 1. Select the waveform next to the message box. 2. Allow your browser to use the microphone, if it asks. 3. Wait until the bar above the box says **Listening**. 4. Talk. You can interrupt Quanta while it's speaking. 5. Select **End voice chat** when you're done. The bar shows what Quanta is doing: **Connecting...**, **Listening**, **Thinking** or **Speaking**. Everything you both say is saved in the chat as text, and the chat is named after the first thing you say. Starting from the Quanta page opens a new chat. Voice chat and phone calls run on Gemini. If you've connected your own Gemini key under **Organization settings**, **AI providers**, they use that key and count toward its monthly spend limit. ## Choose Quanta's voice and language 1. Select the gear at the top of the Quanta page. 2. Open the **Voice** tab. 3. Pick a **Voice**. Select the play button next to it to hear a sample. **Iapetus** is the default. 4. Pick a **Language**: **English (US)**, **English (UK)**, **Spanish (Spain)**, **French**, **German**, **Hindi**, **Portuguese (Brazil)** or **Japanese**. 5. Optionally, describe how Quanta should talk under **Personality & instructions**, for example "Be concise and lead with the impact on uptime." 6. Select **Save**. ![3 Voice. 4 Language. 5 Personality & instructions.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106204006-02-voice-tab.png) The voice and language are used in voice chats and phone calls. **Save** stores all three tabs of **Quanta Settings** together. ## Get phone calls from Quanta Quanta can call you about critical problems and answer when you call it. Calls go through your own Twilio account, so connect Twilio first. 1. Select the gear on the Quanta page and open **Phone & SMS**. 2. Select **Go to Integrations**. ![2 Go to Integrations, when Twilio isn't connected yet.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106205633-03-phone-tab.png) 3. Open **Twilio** and enter your **Account SID**, **Auth Token** and **From Number (E.164)**. The number must be a Twilio number that can make calls and send SMS. 4. Select **Connect**. 5. Back in **Quanta Settings**, open **Phone & SMS** and enter your **Destination phone number** with its country code, for example +44 for the UK. 6. Turn on **Enable phone alerts**. 7. Select **Save**. 8. Select **Test call**. Your phone rings within about 10 seconds and Quanta says the setup works. Once it's set up: - Quanta calls you when a critical alert comes in, such as a monitor going down with a critical incident. It makes at most one alert call an hour. - The Owner can ask Quanta to call them from any chat, for example "Call me about this". - Each call lasts up to 10 minutes and is saved as a chat. A call you asked for from a chat also leaves a short summary in that chat. - To phone Quanta yourself, follow the steps under **Twilio** in **Integrations** to point your Twilio number at Rectify. Then call your Twilio number from the destination number you saved. Heartbeat can also text or call you about what it finds. [Heartbeat: scheduled check-ins and urgent alerts](/rectify/help/a/38-heartbeat-check-ins-and-alerts) explains those options. ### It says "Failed to access microphone. Please check permissions." Your browser blocked the microphone. Allow it for Rectify in your browser's site settings, then try again. ### It says "Voice typing limit reached for this month. Please upgrade your plan." You've used the 30 minutes of dictation included with the Idea plan this month. It resets on the 1st, or upgrade for unlimited dictation. Voice chat isn't affected. ### Test call says "No destination phone number set" The test call rings the number you saved. Enter it, select **Save**, then select **Test call** again. ### I can't change anything in Quanta Settings The settings say "Only the organization owner can change Quanta settings." Ask your organization's Owner to make the change. ## Read next - [Heartbeat: scheduled check-ins and urgent alerts](/rectify/help/a/38-heartbeat-check-ins-and-alerts) - [Set a monthly spend limit on your AI keys](/rectify/help/a/16-set-a-spend-limit-on-your-ai-keys) --- # Heartbeat: scheduled check-ins and urgent alerts Collection: Quanta URL: https://app.rectify.so/rectify/help/a/38-heartbeat-check-ins-and-alerts Turn on Quanta's scheduled reports, choose how often it checks and how it tells you, and read the Project Report. > **Note:** **Before you start.** Only the organization's Owner can turn reports on and change Heartbeat settings. Everyone who can open the project can read the Project Report. Each check uses AI, from your own provider key or your Rectify credits. Heartbeat is Quanta checking your project on a schedule while you're away. Each check ends in a short report in the **Project Report** chat, and urgent problems are posted there as they happen. ## Turn on reports 1. Open **Quanta** in the sidebar. 2. Pick how often Quanta checks, from **Every 10 minutes** to **Every 24 hours**. 3. Select **Turn on reports**. ![2 How often Quanta checks. 3 Turn on reports.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106208219-01-turn-on.png) Quanta runs the first check straight away, and its report is ready in about a minute. **Not now** hides the offer until you come back to the page. ## Choose how often and how Quanta tells you Select the gear at the top of the Quanta page. **Quanta Settings** opens on the **Heartbeat** tab. 1. Turn on **Enable heartbeat**. 2. Pick a **Check interval**. It starts at **Every 6 hours**. 3. Under **Notification Options**, turn on the ways Quanta should reach you. 4. Under **Notification Frequency**, pick the shortest time between two messages on the same channel. It starts at **Every 24 hours**. 5. Select **Save**. ![1 Enable heartbeat. 2 Check interval. 3 Notification Options.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106210064-02-heartbeat-tab.png) | **Option** | **What you get** | | --- | --- | | **Email Notification** | An email with the report | | **Push Notification** | A push notification that opens the Project Report | | **Phone Call** | A call for critical findings. Needs Twilio, a destination number and **Enable phone alerts** on the **Phone & SMS** tab | | **SMS** | A text message. Needs Twilio and a destination number on the **Phone & SMS** tab | All of them start switched off. Quanta uses them when a check finds something that needs you, not for every report. [Talk to Quanta with your voice](/rectify/help/a/37-talk-to-quanta-with-your-voice) shows how to connect Twilio and add your number. The box at the bottom of the tab shows the **Status**, when the last check ran and when the next one is due. ## Read the Project Report Open it from **History**, where **Project Report** is always at the top, or select **Open Project Report** under the report card on the Quanta page. ![The last 24 hours of reports on the Quanta page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106211715-03-report.png) Each report starts with a status, **All clear**, **Needs attention** or **Action required**, followed by a summary, the highlights and what Quanta recommends you do. On the Quanta page, the card lists the reports and alerts from the last 24 hours. The Project Report opens on the latest day with reports. Reports are grouped by day, under **Today**, **Yesterday** or the date, and each one shows the time it came in. To read older ones, select **Show earlier reports** at the top. Each time you select it, one more day loads, and the button shows which day comes next. On each check, Quanta looks at your monitors and incidents, new feedback, code scans, support conversations waiting for a reply, the review queue, analytics, failed workflows, survey scores, Help Center gaps and roadmap changes. ## Urgent alerts Once the Project Report exists, Quanta also posts these to it as they happen, while Heartbeat is on: - A monitor goes down, or comes back up - An incident is escalated to critical - A new bug is reported with critical priority - A visitor asks to talk to a person - A workflow fails - A code scan finds issues, or fails - An analytics alert fires A critical incident, an escalation to critical and a critical bug also call you, if you've set up phone alerts. These alerts are posted to the Project Report only; they don't send email, push or text messages. The same alert is posted once even if it repeats within 5 minutes. ## Turn reports off 1. Select the gear at the top of the Quanta page. 2. Turn off **Enable heartbeat**. 3. Select **Save**. The Project Report and its earlier reports stay in **History**. ## What it costs Each check is an AI request, paid from your own provider key or your Rectify credits. How much a check uses depends on how much is happening in your project, so a longer **Check interval** uses less. Checks are listed as **Heartbeat** on the **Usage** page of Quanta. If your organization has no AI key and no credits left, checks are skipped. ### Teammates see "Reports are off for this project" Only the organization's Owner can turn reports on. Ask them to select **Turn on reports** on the Quanta page. ### The settings say "Only the organization owner can change Quanta settings." You can see the settings, but only the Owner can save them. ### I turned reports on but there's no report yet The first check runs within a minute or two. If nothing arrives, check that your organization has an AI key connected or Rectify credits left under **Organization settings**, **AI providers**. ## Read next - [Ask Quanta and approve its changes](/rectify/help/a/35-ask-quanta-and-approve-changes) - [Talk to Quanta with your voice](/rectify/help/a/37-talk-to-quanta-with-your-voice) --- # How Quanta answers your customers Collection: Quanta URL: https://app.rectify.so/rectify/help/a/39-how-quanta-answers-your-customers What Quanta reads before it answers in your widget, how to keep a source out of its answers, and how to set its name, logo, subtitle and greeting. > **Note:** **Before you start.** Quanta answers in your widget when **Answered by** is set to **Quanta first** or **Quanta only**. [Choose who answers first: Quanta or your team](/rectify/help/a/30-choose-who-answers-first) explains the modes and how chats reach your team. Answers run on your own AI provider key or your Rectify credits. ## What Quanta answers from Before it answers a question, Quanta searches two places: - **Your Help Center:** published articles that everyone can read. Articles set to **Signed-in only**, limited to segments, or marked **Internal only** are never used. - **Your Knowledge base:** your FAQs, websites, documents and API sources, except those marked **Private**. If the first search finds nothing that fits, Quanta tries again with other words, up to three times. Quanta also reads the last few messages of the chat, so customers can ask follow-up questions. > **Important:** If your portal is set to **Private** under **Publish**, **Portal**, **Access**, Quanta can't use any of your Help Center articles in its answers. ## Keep a source out of customer answers 1. Open **Inbox**, then **Knowledge base**. 2. Select **Add FAQ**, then write the **Question** and the **Answer** Quanta should give. 3. To keep it out of customer answers, turn on **Private**. Your team can still find it. 4. To show a link with the answer, turn on **Add a read more link** and fill in **Link title** and **Link URL**. 5. Select **Add FAQ**. ![3 Private. 4 Add a read more link.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106214946-02-faq-private.png) API sources have the same **Private** switch. For a Help Center article, open it in the editor, select **Audience** and turn on **Internal only**. ## Links under Quanta's answers When Quanta answers from a source that has a link, it can list that link under its answer: - **Help Center articles** link to the article. If your widget shows the Help tab, the article opens right inside the widget. - **Website pages** link to the page Quanta read. - **FAQs and documents** link to their read more link, if you added one. ## Questions Quanta couldn't answer When Quanta finds nothing that answers a question, it saves the question for you. Open **Inbox**, **Knowledge base** and select **Unanswered questions** to see them. Pick a few and Quanta drafts FAQs from them, ready for you to check under **Suggested FAQs**. ## Set Quanta's name, logo and greeting 1. Open **Publish**, then **Widget**. 2. Select **Support**. 3. Next to **Quanta's logo**, select **Upload** and pick a JPEG, PNG or GIF up to 10 MB. Left empty, Quanta shows the Rectify logo. 4. Under **Quanta's name**, enter a name of up to 20 characters. Left empty, it's Quanta. 5. Under **Quanta's subtitle**, enter up to 40 characters for the line under the name in the chat header. 6. Under **First message**, write a **Greeting**, or leave it empty for the default welcome. 7. Select **Save** in the bar at the bottom. ![2 Support. 3 Quanta's logo. 4 Quanta's name. 5 Quanta's subtitle.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106216793-01-support-settings.png) With no subtitle, the header says who answers: Quanta, Quanta and the team when you show your team on the home screen, or The team. ## What your customers see ![A chat in the widget preview, with Quanta answering.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106218644-03-preview.png) - The chat header shows your widget's title followed by "support", with the subtitle under it. - Quanta's messages carry its name and logo. - Before their first chat, customers enter their name and email under **Let's get started**. - While they type, **This might answer it** suggests Help Center articles that match. - Customers can attach files once someone from your team has joined the chat. To check it works, open your site, start a chat in the widget and ask something your Help Center answers. ### Quanta doesn't use my Help Center articles Check that the article is published, that its **Audience** is **Everyone** (or **Same as parent** in a collection everyone can read), that it isn't limited to segments or marked **Internal only**, and that your portal isn't set to **Private**. ### Customers see "Something went wrong! Try again" when they send a message Quanta couldn't run, usually because your organization has no AI key and no Rectify credits left. Connect a provider under **Organization settings**, **AI providers**. ### Quanta says "Sorry, I could not find the answer you were looking for" Nothing in your Help Center or Knowledge base answered the question. Add an FAQ for it, or check **Unanswered questions** for more like it. ## Read next - [Choose who answers first: Quanta or your team](/rectify/help/a/30-choose-who-answers-first) - [Set up widget chat, the live support channel](/rectify/help/a/29-set-up-widget-chat) - [What Quanta can do for your team](/rectify/help/a/34-what-quanta-can-do) --- # AI credits and your own AI keys Collection: Quanta URL: https://app.rectify.so/rectify/help/a/40-ai-credits-and-your-own-ai-keys How the Rectify credits on paid plans work, which AI providers you can connect on each plan, how to choose the provider for each feature, and where to see what's used. > **Note:** **Before you start.** Owners and Admins can connect, change and remove AI providers. Members can open **AI providers** to see what's connected, but can't save changes. Credits and keys belong to the organization, so every project in it uses them. Quanta and the other AI features in Rectify run on an AI model. That model comes from your own key with an AI provider, or from the Rectify credits included with paid plans. ## Rectify credits Build, Launch and Accelerate include Rectify credits, so AI features work before you connect a key. Credits run on Deepseek V4 Flash. | **Plan** | **Rectify credits** | | --- | --- | | Idea | None | | Build | $5 | | Launch | $10 | | Accelerate | $15 | - Credits are a one-time amount. They don't renew each month or when your plan renews. - Each AI request uses a little of them, based on how much text the model reads and writes. - When you move between Build, Launch and Accelerate, your credits change to the new plan's amount. What you've already used still counts. - If your paid plan ends, any credits left end with it. - Credits cover text. Features that look at screenshots, images or session replays need a Gemini key of your own. To see what's left: 1. Open **Organization settings**, then **AI providers**. 2. The **Rectify credits** card at the top shows what's left, for example **$14.89 of $15 left**. 3. The provider your credits run on says **Running on Rectify credits**. ![2 Rectify credits. 3 The provider your credits run on.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106221416-01-providers.png) ## How credits and your keys work together - **Your keys come first.** Once you connect a key, it takes over straight away. Credits only step in when none of your keys can answer, for example after a key reaches its monthly spend limit. - **Your own Deepseek key replaces the credits.** While it's connected, AI features use your key and your credits aren't used. Remove the key to go back to the credits. - **When credits run out,** the card says **Used up**. AI features keep running on any key you've connected. With no key, they stop until you connect one. ## Providers you can connect on each plan | **Provider** | **Idea** | **Build, Launch, Accelerate and Enterprise** | | --- | --- | --- | | **Gemini** | Yes | Yes | | **Deepseek** | Yes | Yes | | **Claude** | No | Yes | | **OpenAI** | No | Yes | | **OpenRouter** | No | Yes | | **Kimi** | No | Yes | On Idea there are no credits, so connect a Gemini or Deepseek key to use AI features. ## Connect your own key 1. Open **Organization settings**, then **AI providers**. 2. Select a provider to open it, for example **Claude**. 3. Paste your key under **API key**. 4. Choose a **Model**. Its price per 1M tokens shows under it. 5. Optional: under **Powers**, select **Assign feature** and tick the features this provider should run. 6. Select **Connect**. ![3 API key. 4 Model. 5 Assign feature. 6 Connect.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106223059-02-connect.png) The provider now shows **Connected** with its model. You can also set a **Monthly spend limit** for each key. [Set a monthly spend limit on your AI keys](/rectify/help/a/16-set-a-spend-limit-on-your-ai-keys) explains how. To change a key later, open the provider, make your changes and select **Save changes**. To remove it, select **Remove key**, then **Remove**. Features assigned to that provider move to your other connected providers. ## Choose which provider runs each feature **Powers** decides which of your providers runs which feature. Open a provider, select **Assign feature** and tick a feature. Each one has a short line on what it does, for example **Quanta Chat**, **Support Chat** or **Feedback Triage**. Then select **Save changes**, or **Connect** for a new key. ![The features you can assign under Powers.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106224890-03-powers.png) - Each feature runs on one provider. Once you assign a feature to one provider, it no longer shows in the list for the others. - Features you don't assign use your first connected key, in this order: Deepseek, Claude, OpenAI, Gemini, OpenRouter, Kimi. Your Rectify credits come last. - Powers apply to your own keys. You can't assign features to your credits. ## Best in Quanta's model picker On the Quanta page, the menu next to the microphone shows **Best** until you pick a model. With **Best**, Quanta uses the provider that has **Quanta Chat** under **Powers**. If none has it, Quanta uses your first connected key, and your credits come last. [What Quanta can do for your team](/rectify/help/a/34-what-quanta-can-do) covers the rest of the picker. ## Where to see what's used - **AI providers:** the **Rectify credits** card shows what's left of your credits. - **Quanta, Usage:** on the Quanta page, select **Usage** to see spend and tokens for that project, with filters for **Feature**, **Provider** and **Member**. The **Rectify credits** box shows what's left, and **Which providers** marks each provider's spend as **Rectify credits** or **Your key**. ![Rectify credits on the Usage page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106226710-04-usage.png) - **Billing:** Owners and Admins can open **Organization settings**, **Billing**, select **View all limits** and look for **AI Credits**. ## Troubleshooting ### It says "Upgrade your plan to use Claude" Claude, OpenAI, OpenRouter and Kimi start on the Build plan. [Compare plans and what each one includes](/rectify/help/a/13-compare-plans) lists what each plan has. On Idea, connect a Gemini or Deepseek key. ### It says "This organization's plan does not have access to kimi" Kimi starts on the Build plan. Upgrade, or connect a Gemini or Deepseek key instead. ### It says "Invalid API key" The provider turned the key down. Check you copied the whole key, that it's still active in your provider's account, and that the account has funds. ### The card says "Credits are used up" Your one-time credits are spent. Connect a provider to keep AI features running. ### I don't see Connect or Save changes Only Owners and Admins can change AI providers. Ask one of them to connect the key. ## Read next - [Set a monthly spend limit on your AI keys](/rectify/help/a/16-set-a-spend-limit-on-your-ai-keys) - [Meet Quanta, your AI teammate](/rectify/help/a/7-meet-quanta) - [What Quanta can do for your team](/rectify/help/a/34-what-quanta-can-do) --- # How feedback reaches your inbox Collection: Inbox URL: https://app.rectify.so/rectify/help/a/25-how-feedback-reaches-your-inbox Where bug reports, ideas and testimonials come from, what each one includes, and who hears about a new one. > **Note:** **Before you start.** Feedback arrives once the Rectify widget is on your site. Everyone who can open the project can read its feedback. Session replays and technical logs depend on your plan (see the end of this article). Your users send feedback from the widget on your site. Each report lands in **Inbox**, **Feedback** for that project, newest first. ## The feedback forms in the widget When someone opens the widget, the home screen lists your forms. Each form sends a different type of feedback. | **Form in the widget** | **Type in your inbox** | **Switched on at first** | | --- | --- | --- | | **Report a Bug** | Bug | Yes | | **Share an Idea** | Idea | Yes | | **General Feedback** | General | Yes | | **Share Your Experience** | Testimonial | No | To switch a form on or off, open **Publish**, then **Widget**, and select **Home menu**. Each form has its own switch, and the pencil opens **Edit form**, where you choose its fields. ![The feedback forms in the widget, and their switches under Home menu.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106113310-01-forms.png) Out of the box, a form asks for an email, a title and a description, all required, plus an optional category. You can also switch on a name, a rating, a priority and a checkbox. Titles can be up to 100 characters and descriptions up to 500. People can add one of these to what they write: - **Screenshots:** up to 10, which they can mark up before sending. - **A Loom video:** one, instead of screenshots. - **A file:** one, up to 10 MB. ## What each report includes Open a report to see: - **What they wrote:** the title, the description, the star rating and the checkbox answer (shown as **Form answer**), if the form asked for them. - **Their media:** screenshot thumbnails, **Video** and **Attachment**. - **Who sent it:** the name and email they entered. If your site passes the signed-in user's name and email to the widget, they're filled in for them. With neither, the report shows **Anonymous visitor**. - **Session replay:** bug reports only. A replay of the visit before they sent it, plus console, network and click logs. [Watch a session replay and its debug logs](/rectify/help/a/27-watch-a-session-replay) explains both. ![The report, its screenshot and Session replay, and who sent it.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106114964-02-report.png) The **Session** section under **Details** shows where the report came from: the **Page**, **Country**, **Timezone**, **System**, **Browser**, **Window** size, screen **Resolution**, **DPI** and **Color depth**. ![The page and device details under Session.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106116568-03-session.png) ## Who hears about a new report - **Your team:** everyone who can open the project gets a push notification and an email, with the project's name first. In Acme App, a bug report arrives as **Acme App · New bug reported** and anything else as **Acme App · New feedback received**. The email's subject is **Acme App · New Feedback Received**. Each person can switch these off under **Feedback Received** in their notification settings. - **The person who sent it:** if they left their email, they get a short email to say it arrived. You can edit this email, or stop sending it, under **Project settings**, **Email notifications**, **Feedback Received**. It's sent at first. - **Your other tools:** if you've connected a tool under **Project settings**, **Integrations**, such as Slack, Jira, Linear, GitHub or a webhook, new reports are sent there too. Each integration's settings say what it does with them. [Your profile and notification settings](/rectify/help/a/11-profile-and-notification-settings) shows where each person chooses their alerts. ## Other ways feedback is added - **Quanta:** ask Quanta to log a bug, idea or other feedback for you. It shows what it will create and adds it once you confirm. [Meet Quanta](/rectify/help/a/7-meet-quanta) explains confirming. - **Discord:** once your Discord server is connected, people there can report bugs with /bug, and moderators can send a message to Rectify as a bug report. These land in **Feedback** with **Discord** as their **Source**. Ideas from Discord go to your roadmap instead. [Collect ideas and bug reports from Discord](/rectify/help/a/133-collect-ideas-and-bug-reports-from-discord) explains both. - **Not from the portal or the Chrome extension:** requests on your portal go to your roadmap, and recordings from the Chrome extension go to **Extension sessions**. Neither adds to **Feedback**. ## Plan limits | | **Idea** | **Build** | **Launch** | **Accelerate** | **Enterprise** | | --- | --- | --- | --- | --- | --- | | **Session replays a month** | 10 | 100 | 1,000 | 5,000 | Unlimited | | **Console, network and action logs** | No | Yes | Yes | Yes | Yes | When you reach your session replays for the month, bug reports still arrive, just without a replay. [Compare plans](/rectify/help/a/13-compare-plans) lists every limit. ## Check it worked Open **Inbox**, then **Feedback**. The newest report sits at the top of the list and opens on the right. Until the first report arrives, the page shows **No feedback yet** and a **Set up the widget** button. ### The inbox still says "No feedback yet" Check the widget is on your site and that you're looking at the right project. [The widget doesn't show on my site](/rectify/help/a/24-the-widget-does-not-show) walks through the usual causes. ### A bug report has no session replay Replays come only with **Report a Bug**. Check that **Record sessions** is on under **Publish**, **Widget**, **Privacy**, and that you haven't used this month's session replays. ### The person who sent feedback didn't get an email They may have left the email field empty, or the **Feedback Received** email isn't being sent. Check it under **Project settings**, **Email notifications**. Next, [triage your feedback](/rectify/help/a/26-triage-feedback) with a status, priority and owner. --- # Triage feedback: status, priority, owner and notes Collection: Inbox URL: https://app.rectify.so/rectify/help/a/26-triage-feedback Find feedback fast, set each report's status, priority and assignee, and keep notes your team can see. > **Note:** **Before you start.** Everyone who can open the project can change a report's status, type, priority, category and assignee, and add notes. Only Owners and Admins can move or delete feedback. Open **Inbox**, then **Feedback**. The list is on the left and the report you select opens beside it, with its **Details** on the right. Press **j** and **k** to move down and up the list. ## Find the reports you need 1. Select **Filter** above the list. 2. Pick **Type**, **Status**, **Priority**, **Category** or **Created**, then the values you want. ![1 Filter, with the attributes you can filter by.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106119019-01-filter.png) The sort button next to **Filter** orders the list by **Newest**, **Oldest**, **Recently updated** or **Title A to Z**. The search button on the right looks through titles, descriptions, and reporters' names and emails. To clear every filter, select the **×** next to the sort button. ## Set the status, type and priority 1. Select a report in the list. 2. Under **Details**, open **Status** and pick one. ![2 Status, with the four statuses.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106121307-02-status.png) 3. Set **Type**, **Priority** and **Category** the same way. Each change saves straight away and shows **Feedback updated**. | **Field** | **Choices** | | --- | --- | | **Status** | **Open**, **In Progress**, **Under review**, **Resolved** | | **Type** | **Bug**, **Idea**, **General**, **Testimonial** | | **Priority** | **Low**, **Medium**, **High**, **Critical**, **Neutral** | | **Category** | **Improvement**, **Suggestion**, **Task** (pick any) | New reports start as **Open** with **Neutral** priority, unless your form lets people choose a priority or category. ## Choose who owns it Under **Details**, open **Assignee** and pick a teammate. It saves straight away and shows **Assignee updated**. Your teammate gets an email and a push notification, unless they've switched off **Feedback Assigned to You** in their notification settings. You can hand a report to someone else at any time. There's no option to leave it unassigned again. ## Add a note for your team 1. Below the report, select **Internal note**. 2. Type your note, up to 1,000 characters. 3. Select **Add note**, or press Cmd + Enter. ![1 Internal note. 3 Add note.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106122932-03-notes.png) Reporters never see notes. Each note shows who wrote it and when. Its menu has **Edit**, **Mark resolved** and **Delete**, and anyone on the team can use them. ## Reply to the person who sent it The **Reply to user** tab writes to the reporter. It's greyed out when the report has no email, unless it came from Discord. - If you haven't talked to them yet, **Send invite** emails them an invitation that opens a chat in the widget, on the page they reported from. - If you already have a conversation with them, **Send reply** adds your message to it. **Start a new chat instead** sends a fresh invitation. Your message links back to the report, and the conversation appears in **Inbox**, **Conversations**. On the Idea plan, your team can send 10 Support Inbox replies a month. ### Reply to a bug report from Discord A report sent from your Discord server shows **Discord** next to **Source** under **Details**, and **Discord member** under the reporter's name. **Reply to user** answers them in Discord, through [support chat in Discord](/rectify/help/a/131-set-up-support-chat-in-discord). Next to **Send reply**, a line says where your reply goes: - "Opens a private thread with Noah Bennett in Discord." when private threads are allowed. - "Sends Noah Bennett a direct message in Discord." when only direct messages are allowed. - "Sends to the open Discord chat with Noah Bennett." when they already have a chat open. Select **open Discord chat** to go to it. After you send, you see "Reply sent to Noah Bennett in Discord". In a new chat, your message follows a line saying your team replied about their report. The chat is in **Inbox**, **Conversations**, where you can carry on. If you can't reply in Discord, the line says why and **Send reply** stays greyed out: - "Turn on Support in Discord in Inbox › Channels to reply there." Switch it on in **Inbox**, **Channels**. - "Rectify is paused in this server." Discord is paused for this project in **Integrations**. - "Noah Bennett is in an open direct message chat with another team." They're talking to another team that uses Rectify by direct message. Allow private threads to reply in a thread instead. If the line says "Couldn't check where this reply goes in Discord.", select **Try again**. ## Edit, move or delete a report Open the menu at the top of **Details**: - **Edit:** change the title, description, properties and categories, then select **Save changes**. - **Move:** send the report to another project in your organization. Owners and Admins only. - **Delete:** remove the report with its screenshots and replay. Owners and Admins only. You confirm first, and it can't be undone. To connect a report to a roadmap post, open the post and select **Link** under **Linked**, then search for the feedback. ## Check it worked The status under each title in the list changes as soon as you pick a new one. To see what's left to do, select **Filter**, **Status** and pick **Open**. ### Move and Delete are greyed out You're a Member. Ask an Owner or Admin to move or delete the report. ### Reply to user is greyed out The report has no email address, so there's no one to write to. Reports from Discord don't need one. ### It says "Your team started 30 Discord DMs in the last hour." Your team can start 30 direct message chats in Discord an hour from **Reply to user**. Try again later, or allow private threads under **Inbox**, **Channels**, **Discord**. ### It says the person "turned off direct messages" They don't accept direct messages from your server, so Discord can't deliver the reply. Allow private threads under **Inbox**, **Channels**, **Discord** to reply in a thread instead. ### It says the person "is no longer in your Discord server" They left your server, so Rectify can't open a chat with them there. The reply isn't sent and no chat is created. ### It says "Rectify cannot open a private thread in your support channel." The Rectify role lost a permission in your support channel, or the channel was deleted. Open **Inbox**, **Channels**, **Discord**. Pick another channel under **Support channel**, or allow what the lines under it list in Discord and select **Check again**. ### It says "Replying to reporters needs a higher plan." Your team has used this month's Support Inbox replies on the Idea plan. [Compare plans](/rectify/help/a/13-compare-plans) shows the limits on each plan. ### It says "Cannot invite: this report has no page URL to open the chat on." An invitation opens the chat on the page the report came from, and this report doesn't have one. If you already have a conversation with them, reply there instead. Next, for bug reports, [let Quanta find the cause](/rectify/help/a/28-triage-and-fix-bugs-with-quanta), or [watch the session replay](/rectify/help/a/27-watch-a-session-replay). --- # Watch a session replay and its debug logs Collection: Inbox URL: https://app.rectify.so/rectify/help/a/27-watch-a-session-replay Replay what someone did before they reported a bug, read the console, network and click logs, and choose what gets recorded. > **Note:** **Before you start.** Replays and logs come with bug reports sent from the widget's **Report a Bug** form. Your plan sets how many replays you get each month, and the console, network and action logs need the Build plan or higher. When someone sends a bug report, the widget attaches a replay of what they did on the page before they sent it, and technical logs from their browser. You can watch the replay and read the logs next to the report. ## Open a replay From the report: 1. Open **Inbox**, then **Feedback**, and select a bug report. 2. Select **Session replay** under the description. **Media Preview** opens on the **Session Replay** tab. Or from the list of every replay: 1. Open **Inbox**, then **Session replays**. Each row shows the report, the reporter, their location, browser and how long the session was. 2. Select **Play** on a row. ![2 Play, on a session in Session replays.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106125946-01-session-replays.png) ## Watch it The replay starts paused. Play it, drag along the timeline, or switch to double speed. Quiet stretches are skipped as it plays. Beside the replay: - **Event Timeline** lists what happened, in order: **User Actions**, **Navigation**, **Page Changes** and **System**. Turn on **Major only** to hide the small stuff, or search the events. Select an event to jump the replay to that moment. - **Analysis & Chat** asks Quanta about the session. Select **Let's GO!** for a summary of what the person did, then ask follow-up questions. It uses your AI credits or your own AI key. ## Read the technical logs On the report, select **Technical logs** next to **Session replay**. The **Technical Logs** panel has three tabs: - **Console:** messages from their browser's console: logs, info, warnings and errors. Filter by text or by level. - **Network:** the requests the page made, with each one's address, method and status, and a count of failed ones. It lists requests sent with XMLHttpRequest, which libraries such as axios use. Requests made with `fetch()` aren't recorded. - **User Actions:** their clicks, keys like Enter and Tab, scrolls, page changes and form submits, in order. The characters they type are never logged. On the Idea plan, the three tabs are locked. Select **Upgrade to Build** (or **Start 14-day trial**, if you can still start one) to open them. ## What gets recorded The widget records while it's on the page. A replay covers about the last four minutes before the report, and recording starts again each time the page loads. Some things are never recorded: - What people type in password fields. - The characters people type, anywhere on the page. **User Actions** only lists keys like Enter, Tab and Escape, and nothing from password fields. - Passwords, tokens, API keys, cookies, card numbers and one-time codes in the requests the page makes, whether they're in the address, the headers or the body. They show as `[REDACTED]`. - What's sent to sign-in, sign-up and password reset addresses, apart from details like the email address and error messages. It shows as `[REDACTED]` too. - The text in fields people click on. The logged click shows `[REDACTED]` instead. ## Choose what's recorded 1. Open **Publish**, then **Widget**, and select **Privacy**. 2. Under **Session replay**, switch **Record sessions** and **Capture technical logs** on or off. 3. Under **Masking**, choose what to hide: - **Mask all text:** every word on the page is hidden in the replay. - **Mask all inputs:** everything people type is hidden. - **Always mask these inputs:** pick field types to hide, such as **Email** or **Telephone**. **Password** is always masked. - **Mask by class**, **Block by class** and **Ignore by class:** enter a CSS class name. Elements with it are hidden, left out of the replay, or not recorded when people type in them. 4. Select **Save**. ![2 Record sessions. 3 Mask all text, with the other masking options.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106127582-02-privacy.png) The changes apply the next time a page with the widget loads. ## Check it worked Send a test report with **Report a Bug** from your site. In **Inbox**, **Feedback**, the report shows **Session replay**, and **Technical logs** when logs were captured. ### A bug report has no Session replay Check that **Record sessions** is on under **Privacy**. Replays come only with **Report a Bug**, and stop for the month when you reach your plan's session replays. The report still arrives without one. ### There's no Technical logs button **Capture technical logs** is off under **Privacy**, or the report isn't a bug report. ### The Network tab doesn't show requests I expected Only requests sent with XMLHttpRequest are recorded. Requests your app makes with `fetch()` don't appear. To find the cause of a bug from its logs, [triage it with Quanta](/rectify/help/a/28-triage-and-fix-bugs-with-quanta). --- # Triage and fix bugs with Quanta Collection: Inbox URL: https://app.rectify.so/rectify/help/a/28-triage-and-fix-bugs-with-quanta Let Quanta find the likely cause of a bug report, point to the code, and open a draft pull request with a fix for you to review. > **Note:** **Before you start.** Triage works on bug reports. Anyone who can open the project can run it, and it uses your organization's AI: your own AI provider key, or the AI credits included with paid plans. To have Quanta write a fix, you also need GitHub connected with a repository, and your own AI provider key, since credits can't be used for fixes. Only Owners and Admins can start a fix. Quanta reads everything captured with a bug report (the description, console errors, failed requests, clicks and screenshots) and, with GitHub connected, your code. It explains what most likely broke and where, and can open a draft pull request with a fix. ## Triage a bug report 1. Open **Inbox**, then **Feedback**, and select a bug report. 2. Select **Triage with Quanta** at the top of **Details**. ![2 Triage with Quanta, above the reporter.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106131647-01-triage-button.png) 3. Optionally, pick a **Model**. **Auto (recommended)** lets Rectify choose. 4. Select **Start triage**. ![3 Model. 4 Start triage.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106133316-02-start-triage.png) Quanta works through **Diagnostics**, **Screenshots**, **Repository**, **Suspect code** and **Report**. You can close the panel while it runs. You get a push notification when the report is ready, and the button changes to **Quanta Report**. Screenshots are read with Gemini, so Quanta looks at them only when you've added your own Gemini key under **Organization settings**, **AI providers**. It reads up to three. ## Read the report Select **Quanta Report** to open it. The report shows: - the **severity** and a **suggested priority**. The report's own **Priority** doesn't change until you set it. - a short summary of what happened. - **Likely root cause**, with how confident Quanta is and the evidence behind it. - **Suspect files**, linked to your repository on GitHub. - **Reproduction steps** and **Suggested fixes**. To run it again, for example after connecting GitHub, select **Re-triage** in the panel. Without GitHub, Quanta works only from what was captured with the report. To add your code, select **Connect GitHub** (or **Connect GitHub to enable automated fixes**), then **Connect GitHub Account**, and approve Rectify on GitHub. Back in Rectify, pick the **Repository** and select **Save**. Then run the triage again. ## Let Quanta fix it 1. In the report, select **Fix with Quanta**. 2. Read **Let Quanta fix this bug?**. Quanta copies your repository into a sandbox, writes a fix guided by the report, runs tests where it can, and opens a draft pull request. 3. Select **Start fix**. The panel follows the work: **Queued**, **Cloning repository**, **Quanta is writing a fix**, **Validating changes** and **Opening draft pull request**. When it's done, you see **Quanta opened a draft pull request**, the files it changed and what it cost on your key. Select **View draft PR** to review it on GitHub. Nothing is merged without your review, and Quanta never pushes to your default branch. The pull request stays a draft until you mark it ready. **Fix with Quanta** doesn't show when Quanta concluded the report needs no code change, or when GitHub access failed during the triage. In both cases, fix the cause and run the triage again. ## Ask Quanta about a report For questions the report doesn't answer, select **Ask Quanta** below the report and type your question. The **Session logs**, **Screenshots** and **Attachment** buttons include or leave out each one. Reading screenshots needs your own Gemini key. ## Check it worked The button at the top of **Details** reads **Quanta Report**, with a dot in the colour of the severity. After a fix, **View draft PR** opens the pull request on GitHub. To get a push notification when a triage or a fix finishes, keep **Quanta Triage Complete** and **Quanta Draft PR Ready** on in your [notification settings](/rectify/help/a/11-profile-and-notification-settings). ### It says "AI API key not found" Your organization has no AI key and no AI credits left. Add a key under **Organization settings**, **AI providers**. ### It says "Add an AI provider API key in AI settings to use Quanta fixes" Fixes run on your own AI provider key, not on credits. Add a key under **Organization settings**, **AI providers**. ### It says "Admin access required" when I start a fix Only Owners and Admins can start a fix. Ask one of them, or ask for the Admin role. ### It says "Triage is already running for this feedback" or "A Quanta fix is already in progress for this feedback" Wait for the current run to finish. If a run seems stuck, you can start a new triage after 10 minutes, or a new fix after 30. ### It says "Quanta triage failed" Open the panel and select **Start triage** to run it again. If it fails again, pick another **Model** first. [Meet Quanta](/rectify/help/a/7-meet-quanta) covers everything else Quanta can do, and [Set a spend limit on your AI keys](/rectify/help/a/16-set-a-spend-limit-on-your-ai-keys) keeps AI costs in check. --- # Set up widget chat, the live support channel Collection: Inbox URL: https://app.rectify.so/rectify/help/a/29-set-up-widget-chat Turn on live chat in your widget's Support tab, choose its first message, and check that it's live on the Channels page. > **Note:** **Before you start.** The Rectify script needs to be on your site. [Install the Rectify widget on your site](/rectify/help/a/5-install-the-rectify-widget) shows how. Owners, Admins and Members can change widget settings. Widget chat is the **Support** tab in your Rectify widget. Every chat from it lands in **Inbox**, **Conversations**. ## Your support channels Open **Inbox**, then **Channels**. - **Live** lists where customers reach you today. **Widget chat** shows **Live** while the widget is switched on for your site, or **Off** when it isn't. Next to that, you see who answers and how many conversations started in the last 30 days. **Discord** is listed here too. [Set up support chat in Discord](/rectify/help/a/131-set-up-support-chat-in-discord) shows how to turn it on. - **Planned** lists channels that aren't available yet: Messenger, WhatsApp, X and Telegram. They're marked **Coming soon**. On a wide screen, the right side shows widget chat as your visitors see it. Switch between **Desktop** and **Mobile** to compare. ## Set up the chat 1. Open **Inbox**, then **Channels**. 2. Select **Settings** next to **Widget chat**. Your widget settings open on **Support**. ![2 Settings, next to Widget chat.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794938308606-01-channels.png) 3. Under **Answered by**, pick who answers: Quanta, your team, or Quanta first. [Choose who answers first: Quanta or your team](/rectify/help/a/30-choose-who-answers-first) explains each one. 4. Under **Greeting**, write what customers read when a chat opens, up to 1,000 characters. Leave it empty to use the default greeting. 5. Under **Start button**, change the button label if you like, for example "Chat with us". The default is **Start a conversation**. The same label is on the Support card in the **Support only** layout. 6. To suggest questions above the message box, switch on **Quick bubbles** and select **Add prompt** for each one. 7. Select **Save**. ![4 Greeting. 5 Start button. 6 Quick bubbles.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106137911-02-first-message.png) More options on the same tab: - **Show your team on the home screen** shows your team's photos next to the widget title. Under **Who appears**, **All** shows everyone you pick, and **Online** shows only people who have Rectify open right now. Tick people under **Pick the people**. - **Quanta's logo**, **Quanta's name** (up to 20 characters) and **Quanta's subtitle** (up to 40 characters) change how Quanta appears in the chat. - **Special notice at the top** shows a banner in every conversation while it's on, for example when replies may be slower. Write it under **Notice text**, up to 500 characters. - **Lock closed conversations** stops customers replying to a conversation marked done. They start a new one instead. ## Make sure the widget shows chat 1. Select **Look**. 2. Under **Bottom navigation**, check that the **Support** switch is on. It's on by default. In a widget set up a while ago, this tab may be called **Messages**. Open the row to change its icon or **Label**. ![2 The Support tab switch.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106139954-03-bottom-nav.png) 3. Select **Install**. 4. Under **Status**, check that **Widget on your site** is on. 5. If you changed anything, select **Save**. ![3 Install. 4 Widget on your site.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106141631-04-install-status.png) ## Make a support-only widget To make chat the only thing visitors see, open **Publish**, then **Widget**, select **Home menu**, and select **Support only** under **Layout**. Visitors then get a chat card under your greeting, with no other cards and no tab bar. [Choose the widget's layout](/rectify/help/a/126-choose-the-widgets-layout) explains each layout. ## What your customers see 1. They open the widget and select **Support**. 2. The first time, they enter their name and email under **Let's get started**, then select **Continue**. 3. Your greeting opens the chat, and they type their question. 4. When they come back later, the tab lists their earlier conversations, with your start button for a new one. When your team replies and the customer isn't on your site, they get an email with a link back to the conversation. Once a chat is with your team, customers can attach an image or a PDF, up to 10 MB. When you mark a conversation done, the customer sees **Conversation closed** and can select **Download** to save a copy of the chat. If a conversation can't open on the device they're using, they see **Can't open this chat here** and can select **Email me a link** to carry on. ## Check it worked 1. Open your site and open the widget. 2. Select **Support** and start a conversation. 3. In Rectify, open **Inbox**, then **Conversations**. Your chat is in the list once you've sent a message. While Quanta is answering it, Quanta's face shows next to it. ## Troubleshooting ### Widget chat says Off on the Channels page The widget is switched off for your site. Open **Publish**, **Widget**, select **Install**, switch on **Widget on your site** and select **Save**. ### There's no Support tab in the widget Open **Publish**, **Widget**, select **Look**, and switch on **Support** under **Bottom navigation**. In a widget set up a while ago, it may be called **Messages**. Then select **Save** and reload your site. ### My changes don't show in the widget Select **Save** at the bottom of the widget settings, then reload the page on your site. [The widget doesn't show on my site](/rectify/help/a/24-the-widget-does-not-show) has more checks. ## Read next - [Choose who answers first: Quanta or your team](/rectify/help/a/30-choose-who-answers-first) - [Choose the widget's layout](/rectify/help/a/126-choose-the-widgets-layout) - [Set up support chat in Discord](/rectify/help/a/131-set-up-support-chat-in-discord) - [Answer chats in the support inbox](/rectify/help/a/32-answer-chats-in-the-support-inbox) --- # Set up support chat in Discord Collection: Inbox URL: https://app.rectify.so/rectify/help/a/131-set-up-support-chat-in-discord Let people in your Discord server get help in a private thread or a direct message, answered by Quanta and your team from Conversations. > **Note:** **Before you start.** Your Discord server needs to be connected to the project. [Connect Discord](/rectify/help/a/132-connect-discord) shows how. Discord chats use your widget chat's answers and hours, so [set up widget chat](/rectify/help/a/29-set-up-widget-chat) first. Owners, Admins and Members can change these settings. On the free Idea plan, your team's replies to Discord chats count toward its 10 Support Inbox replies a month. With support chat in Discord, people in your server ask for help with **/support** or a **Get help** button. The chat opens in a private thread or a direct message. Quanta answers first if your widget chat works that way, and your team replies from **Inbox**, **Conversations**, next to your widget chats. ## Turn on support chat 1. Open **Inbox**, then **Channels**. 2. Under **Live**, find **Discord**. Its settings open below it. **Settings** hides or shows them. 3. Under **Where chats happen**, pick **Private threads**, **Direct messages** or **Both**. With **Both**, people pick when they ask. 4. If chats can open in private threads, pick a channel under **Support channel**. Each private thread opens in that channel. 5. Switch on **Support in Discord**. 6. Under **Get help message**, select **Post**. Rectify posts a message with a **Get help** button in your support channel. ![3 Where chats happen. 4 Support channel. 5 Support in Discord. 6 Post.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794938259297-01-settings.png) Each change saves straight away. With private threads allowed, **Support in Discord** stays greyed out until you pick a support channel. With **Direct messages** only, there's no support channel. Pick the channel for the Get help message next to **Post** instead. Its button opens a chat in direct messages. The Get help message says "Need help with Acme App?" and "Press Get help to chat with the Acme App team in private.", with your project's name. **Post again** posts a fresh one and removes the old one, for example when you want it in another channel. Switching **Support in Discord** off stops new chats. Chats that are already open can still be answered. ## Fix the support channel's permissions When you pick a support channel, Rectify checks its permissions in Discord. If something is missing, lines under **Support channel** say what: - "Rectify can't open private threads in" your channel: the Rectify role needs the permissions it lists. Until it has them, **Support in Discord** can't use that channel. - "People may not be able to use their private thread in" your channel: everyone, or the roles that ask for help, need the permissions it lists to see the channel and write in their thread. Chats can still open. In Discord, open the channel's **Edit Channel**, then **Permissions**, and allow what's listed. Then select **Check again**. ![The permission lines and Check again under Support channel.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794938261253-02-channel-problems.png) ## Approve new permissions in Discord If you connected Discord before support chat was available, Rectify needs a few more permissions in your server. The Discord row shows **Needs approval**, and a box above the settings says **Approve new permissions in Discord**. It lists the permissions, for example **Create Private Threads**, **Send Messages in Threads**, **Manage Threads** and **Manage Webhooks**. 1. Select **Approve in Discord**. ![1 Approve in Discord, next to the permissions it asks for.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794938264333-03-approve.png) 2. In Discord, approve the permissions for your server. You need **Manage Server** in that server. Discord brings you back to Channels with "Discord permissions approved. Support chats can open in your server now." ## Answers come from widget chat Discord chats follow your widget chat's settings. **Answers** in the Discord settings shows the current **Answered by**, **Lock closed conversations** and **Operating hours**. To change them, select **Change in Widget › Support**. [Choose who answers first: Quanta or your team](/rectify/help/a/30-choose-who-answers-first) explains each choice. ## Who can start a chat The note at the bottom of the Discord settings sums it up: - Everyone in your server can use **/support** and the **Get help** button. - **Move to support** is for people who can manage messages, such as your moderators. To change who can use each one, open your server in Discord and go to **Server Settings**, **Integrations**, **Rectify**. ## What people in your server see Each person can have one open chat with your project at a time. ### Starting a chat - **/support:** they type /support and their question. Questions can be 3 to 1,500 characters. - **Get help:** the button on your Get help message opens a short form that asks "What do you need help with?". - **Move to support:** a moderator picks **Move to support** from the **Apps** menu on someone's message. The chat opens for the person who wrote it, and their message and its files become the first message. The conversation shows who moved it. With **Both**, Rectify asks "Where do you want to chat with the Acme App team?" with **Private thread** and **Direct messages** buttons. Messages a moderator moves open in a private thread when threads are allowed, and by direct message otherwise. ### Private thread or direct message - **Private thread:** Rectify opens a thread called "Support · " and the person's name in your support channel, adds them to it and posts their question. Only they see the reply "Your chat is open:" with a link to the thread. - **Direct message:** Rectify sends them a direct message that starts "You are chatting with the Acme App team from Acme Community. You asked:" and their question. If they don't accept direct messages from the server, Rectify tells them how to turn them on, and offers a private thread instead when threads are allowed. If they ask again while their chat is open, Rectify replies "You already have an open chat:" with a link to it. A chat you've marked **Done** doesn't count. ### Who answers - **Quanta first:** Quanta answers from the same help content as widget chat, under the name and picture you gave Quanta in your widget settings. Its answers have a **Talk to our support team** button, and the chat moves to your team when the person selects it, just like in the widget. - **Quanta only:** Quanta answers everything, and the button never shows. - **Team only:** the chat goes straight to your team. If you've set operating hours and it's outside them, the person gets your away message. Your team's replies show in the thread or direct message with the teammate's name. [Answer chats in the support inbox](/rectify/help/a/32-answer-chats-in-the-support-inbox) covers replying. ### When a chat is done When you mark a chat **Done**, the thread or direct message gets "Conversation marked as done". - With **Lock closed conversations** off, the person can keep writing in the same chat. - With it on, the thread is locked. In a direct message, a later message gets "This chat is closed. Use /support in Acme Community to start a new one." **Reopen** unlocks the thread and posts "Conversation reopened". ## Check it worked In **Channels**, the Discord row shows **Live**, who answers, your server, where chats happen and how many conversations started in the last 30 days. ![The Discord row, live.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794938266360-04-live.png) Then type /support with a question in your server. The chat appears in **Inbox**, **Conversations** with the Discord mark next to it. | **The row shows** | **What it means** | | --- | --- | | **Live** | People can start chats. | | **Off** | **Support in Discord** is switched off. | | **Paused** | Discord is paused in **Integrations**. Nothing comes in until you switch it back on. | | **Needs approval** | Rectify needs new permissions in your server. Select **Approve in Discord**. | | **Not connected** | Discord isn't connected to this project. Select **Connect**. | | **Removed** | Rectify was removed from your server, so chats there can't get replies. Select **Add it again**. | ## Troubleshooting ### Support in Discord is greyed out Pick a support channel first. While private threads are allowed, support needs a channel to open them in. ### Post is greyed out Switch on **Support in Discord** first. If it says "Rectify can't post in #help", allow **Send Messages** and **Embed Links** for the Rectify role in that channel, then come back to Channels. ### It says "Rectify can't see any text channel." Give the Rectify role **View Channel** on at least one text channel in Discord, then come back to Channels. ### People get "Support chat is not turned on for this server." Switch on **Support in Discord** in **Inbox**, **Channels**. ### People get "Rectify is paused in this server." Discord is paused for this project in **Integrations**. Switch it back on there. ### People get "You have sent a lot in a short time." Each person can send Rectify 5 questions, ideas or bug reports in 10 minutes, and a server 300 a day. They can try again in a few minutes. ## Read next - [Answer chats in the support inbox](/rectify/help/a/32-answer-chats-in-the-support-inbox) - [Choose who answers first: Quanta or your team](/rectify/help/a/30-choose-who-answers-first) - [Connect Discord](/rectify/help/a/132-connect-discord) --- # Choose who answers first: Quanta or your team Collection: Inbox URL: https://app.rectify.so/rectify/help/a/30-choose-who-answers-first Decide whether Quanta, your team, or Quanta and then your team answer chats in the widget, and see how a chat moves to your team. > **Note:** **Before you start.** Owners, Admins and Members can change widget settings. Quanta answers with your organization's AI provider, or with the Rectify credits included with paid plans. ## Pick who answers 1. Open **Publish**, then **Widget**. 2. Select **Support**. 3. Under **Answered by**, pick **Quanta first**, **Quanta only** or **Team only**. 4. Select **Save**. ![2 Support. 3 Answered by.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106144524-01-answered-by.png) | **Option** | **What happens** | | --- | --- | | **Quanta first** | Quanta answers every new chat, and hands over to your team when it can't help. This is the default. | | **Quanta only** | Quanta answers everything. Customers can't reach your team from the chat. | | **Team only** | Every chat goes straight to your team in **Conversations**. Quanta doesn't answer. | Quanta answers from your published Help Center articles and your Knowledge base. Internal and sign-in-only articles are never used. The more you publish, the more Quanta can answer on its own. A change also reaches chats that are already open, at the customer's next message. After a switch to **Team only**, the chat moves to your team. After a switch to **Quanta only**, a chat with your team goes back to Quanta. Chats from your Discord server follow the same choice and the same hours. [Set up support chat in Discord](/rectify/help/a/131-set-up-support-chat-in-discord) explains how they work there. ## How a chat reaches your team With **Quanta first**: 1. Quanta looks for the answer in your articles. When it finds none, or the customer asks for a person, its reply ends with a **Talk to our support team** button. 2. The customer selects the button. They see "Your request for human support has been received. A support agent will join the conversation shortly." 3. The chat moves into **Conversations** with nobody assigned and the priority set to **Medium**. Your team gets a **Human Support Requested** alert. 4. Someone on your team selects **Join** and replies. From then on, Quanta stays out of that chat. [Answer chats in the support inbox](/rectify/help/a/32-answer-chats-in-the-support-inbox) covers replying. ## Step in before a handover You don't have to wait for the customer to ask. Chats that Quanta is still answering are in the conversation list too, with Quanta's face next to them. 1. In **Conversations**, select a chat with Quanta's face next to it. 2. Select **Take over** in the bar at the bottom of the chat. ![1 A chat Quanta is answering. 2 Take over.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794742128640-02-quanta-chats.png) The chat is assigned to you, and the customer sees "You're now connected with our support team for personalized assistance." **Take Over** at the top of the chat does the same. A Quanta reply marked **Escalated** is one where Quanta offered the customer your team. To see only the chats Quanta is answering, select the Quanta button at the top of the list. Select it again to show every conversation. ## When your team is away You can set your team's hours and a message for customers who ask for your team while you're away. 1. Under **Availability**, select **Manage hours**. 2. Switch on **Reply automatically outside operating hours**. 3. Pick your **Timezone**. 4. Under **Hours**, set the days and times your team is around. **Add hours** adds another set of days. 5. Write your **Message**, or keep the default. 6. Select **Save hours**. The hours save straight away, separately from the rest of the widget settings. ![2 Auto reply. 3 Timezone. 4 Hours. 5 Message. 6 Save hours.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106148249-03-hours.png) While the banner above a conversation in **Conversations** says **Outside support hours**, a customer who asks for your team gets your message instead of the usual handover message. Quanta keeps answering around the clock. ## Check it works Open your site, open the widget and select **Support**. Start a conversation and ask something your articles don't cover. With **Quanta first**, select **Talk to our support team** when it appears. In **Conversations**, the chat loses Quanta's face in the list and is ready for your team to join. ## Troubleshooting ### Quanta doesn't answer, and the chat says "Something went wrong! Try again" Quanta needs an AI provider or Rectify credits. Ask an Owner or Admin to check **Organization settings**, **AI providers**. ### Customers never see Talk to our support team On **Quanta only**, Quanta never offers your team. On **Quanta first**, the button only shows when Quanta can't help or the customer asks for a person. ### A chat I took over went back to Quanta On **Quanta only**, a chat goes back to Quanta at the customer's next message. Switch to **Quanta first** to keep chats with your team. ## Read next - [Set up widget chat, the live support channel](/rectify/help/a/29-set-up-widget-chat) - [Set up support chat in Discord](/rectify/help/a/131-set-up-support-chat-in-discord) - [Answer chats in the support inbox](/rectify/help/a/32-answer-chats-in-the-support-inbox) --- # Teach Quanta with the knowledge base Collection: Inbox URL: https://app.rectify.so/rectify/help/a/31-teach-quanta-with-the-knowledge-base Add FAQs, websites, documents and API sources for Quanta to answer customers from, keep some private to your team, and turn unanswered questions into new FAQs. > **Note:** **Before you start.** Everyone who can open a project can add and edit its sources. Only Owners and Admins can delete them. Each project has its own knowledge base, and nothing in it is published to your Help Center or portal. The knowledge base holds what Quanta answers from besides your Help Center: questions and answers, websites, documents, and API sources that look up live details. To open it, select **Inbox**, then **Knowledge base**. Each type has its own list under **Sources**, and **Needs an answer** collects the questions Quanta couldn't answer. ![The Knowledge base, with Add content at the top.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106150914-01-sources.png) ## What you can add Select **Add content** and pick a type. | **Type** | **What Quanta does with it** | **Private** | **Read more link** | | --- | --- | --- | --- | | **FAQ** | Gives your answer when a customer asks that question | Yes | Yes | | **Website** | Reads the site's pages and keeps them up to date | No | Links the page it read | | **Document** | Answers from the text of a PDF, text or Markdown file | No | Yes, once uploaded | | **API source** | Calls your API to look up live details for a customer, like an order status | Yes | No | ![The four types in Add content.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106152951-02-add-content.png) ## Add an FAQ 1. Select **Add content**, then **FAQ**. 2. Enter the **Question**, as your customers would ask it. 3. Enter the **Answer** Quanta should give. The more detail, the better. 4. Optional: turn on **Private** to keep this out of answers to customers. 5. Optional: turn on **Add a read more link**, then fill in **Link title** and **Link URL**. Quanta shares this link when it answers from the FAQ. 6. Select **Add FAQ**. ![2 Question. 3 Answer. 4 Private. 5 Add a read more link. 6 Add FAQ.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106154753-03-faq.png) To change an FAQ, open the menu (**...**) on its row, select **Edit**, make your changes and select **Save changes**. ## Add a website 1. Select **Add content**, then **Website**. 2. Enter the **Website address**. 3. **Choose page parts** is on to start with. To read only part of each page, enter **CSS selectors**. Leave it empty to read whole pages. 4. Optional: turn on **More options** to fill in **Skip these paths**, separated by commas, and the **Link depth**: how many links away from the address Quanta goes, from 1 to 10. Each path you skip is added to the website address, so `/pricing` on `https://acme.example` skips `https://acme.example/pricing`. 5. Select **Add website**. ![2 Website address. 3 Choose page parts. 4 More options. 5 Add website.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106157512-04-website.png) Quanta starts reading straight away. The website shows **Reading pages** with a count, then **Active** with the number of pages read and when it last read them. Quanta reads up to 500 pages, and only pages on the same site. It checks every day and reads each website again every 7 days. To read a website again now, or change its options, select **Read again**, then **Save changes**. The address can't be changed. To read a different address, add it as a new website. ## Upload a document 1. Select **Add content**, then **Document**. 2. Drop a file in the box, or click to choose one. It can be a PDF, TXT or Markdown file, up to 20 MB. Quanta turns the file into text and answers from it. To fix that text or add a read more link, open the menu (**...**) on the document and select **Edit**. Change the **Text**, turn on **Add a read more link** if you want one, then select **Save changes**. ![The text Quanta answers from, and a read more link.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106159339-05-document.png) ## Add an API source An API source lets Quanta look up something live for a customer, like where their order is. When a customer asks for it, Quanta shows them a short form. When they send it, Rectify sends a POST request with their answers to your endpoint, and Quanta explains the reply in the chat. 1. Select **Add content**, then **API source**. 2. Under **Function**, enter a **Name**. Customers see it as the title of the form. 3. Enter **What it does**. Quanta reads it to decide when to use the source, and customers see it on the form. 4. Under **Request**, enter the **Endpoint**. Requests are always sent as POST. 5. To add a header your API needs, like **Authorization**, select **Add header** and fill in its name and value. You can add up to 10. ![2 Name. 4 Endpoint. 5 A header.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106162163-06-api-request.png) 6. Under **Parameters**, describe each field the customer fills in: - **Field name**: sent to your API under this name. - **Type**: **String**, **Number** or **Boolean**. - **Hint for the customer**: shown inside the field on the form. - **Allowed values**: optional, for **String** fields. Separate them with commas. - **Required**: turn on if the customer must fill it in. - **Add parameter**: adds another field. 7. Select **Add API source**. ![6 Field name. 7 Add API source.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106164031-07-api-parameters.png) > **Warning:** Use a key that can only reach what Quanta needs. Everyone who can open the project can see the headers when they edit the source. ## Keep a source private FAQs and API sources have a **Private** switch. A private source: - is never used when Quanta answers customers, and Quanta never offers a private API source's form - shows a **Private** tag in the list - can still be found by your team, including Quanta on the Quanta page. Websites and documents don't have the switch. To keep one out of customer answers, delete it. ## How Quanta uses your sources - **In the widget:** before it answers, Quanta searches your published Help Center articles and every knowledge base source that isn't private. When the answer comes from a source with a link, Quanta can list the link under its answer. [How Quanta answers your customers](/rectify/help/a/39-how-quanta-answers-your-customers) covers this in detail. - **In Conversations:** chats Quanta is answering from your sources show in the list with Quanta's face next to them. [Choose who answers first: Quanta or your team](/rectify/help/a/30-choose-who-answers-first) explains how a chat moves to your team. When you ask Quanta to draft a reply there, it works from the conversation and the customer's earlier chats and feedback, not from the knowledge base. - **On the Quanta page:** Quanta searches every source, private ones too, when your question needs them. You can also ask it to add an FAQ. It asks you to confirm first. ## Turn unanswered questions into FAQs When Quanta finds nothing that answers a customer's question, it saves the question with the customer's email, or **Anonymous visitor**. 1. Under **Needs an answer**, select **Unanswered questions**. 2. Tick the questions you want to work on, or **Select all**. 3. Select **Generate suggestions**. ![1 Unanswered questions. 2 Pick questions. 3 Generate suggestions.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106165460-08-unanswered.png) 4. Open **Suggested FAQs**. Quanta has merged questions that ask the same thing into clear ones. 5. Open the menu (**...**) on a suggestion and select **Edit**. 6. Write the **Answer**, then select **Add FAQ**. The suggestion moves to your FAQs. Generating suggestions runs on your AI provider or your Rectify credits. Unanswered questions and suggestions are kept for a year. ## Limits | | **Limit** | | --- | --- | | FAQ question | 3 to 200 characters | | FAQ answer | 10 to 2,000 characters | | Link title and Link URL | Up to 200 characters each | | Document upload | One PDF, TXT or Markdown file at a time, up to 20 MB | | Document text when you edit it | 10 to 8,000 characters | | Website | Up to 500 pages on the same site, link depth 1 to 10 | | API source | Up to 10 headers, POST requests only | ## Check it works Open your site, open the widget and select **Support**. Ask something one of your FAQs answers. Quanta answers from it, with your read more link if you added one. You can also ask the same question on the Quanta page. ## Troubleshooting ### A website shows Failed Quanta reads public pages only. Check the address opens in a private browser window without a sign-in, then select **Read again** and **Save changes**. ### It says "Use a comma followed by a single space." under CSS selectors With **More options** on, **CSS selectors** only takes plain element names, like `p, article`. To use a class or ID like `.content`, turn off **More options**. ### It says "File content cannot exceed 8000 characters" Edits to a document's text save up to 8,000 characters. For a longer file, change the file itself and upload it again. ### Customers see "I encountered an error while processing your form submission" Your endpoint returned an error or couldn't be reached. Check the **Endpoint** and headers on the API source, and that your API accepts a POST request with the fields you set up. ### Delete is greyed out Only Owners and Admins can delete sources and suggestions. Ask one of them, or turn on **Private** for an FAQ or API source instead. ## Read next - [How Quanta answers your customers](/rectify/help/a/39-how-quanta-answers-your-customers) - [Choose who answers first: Quanta or your team](/rectify/help/a/30-choose-who-answers-first) --- # Answer chats in the support inbox Collection: Inbox URL: https://app.rectify.so/rectify/help/a/32-answer-chats-in-the-support-inbox Reply to customers in Conversations, let Quanta draft with you, keep private notes, and close or archive a chat. > **Note:** **Before you start.** Everyone on your team can open Conversations, join a chat and reply. **Done**, **Archive**, delete, **Priority** and notes are for Owners and Admins. On the free Idea plan, your team can send 10 replies a month. Chats from your widget's **Support** tab reach your team in **Conversations**, and so do chats from your Discord server once you [set up support chat in Discord](/rectify/help/a/131-set-up-support-chat-in-discord). Open it from **Inbox**, then **Conversations**. ## Find a conversation The list shows the conversations handed to your team and the chats Quanta is still answering. Unread ones sit at the top with a dot, and the number next to **Inbox** and **Conversations** in the sidebar counts them. A chat Quanta is answering has Quanta's face next to its last message, and it joins the list once the customer sends their first message. If you've set **Quanta's name** or **Quanta's logo** in your widget settings, you see those instead. - **Filter** narrows the list by **Status** (**Open**, **Done** or **Archived**), **Assignee**, **Channel** (**Widget chat** or **Discord**) or **Priority**. Under **Assignee**, **Assigned** means assigned to you. - The Quanta button at the top of the list shows only the chats Quanta is answering. Select it again to show every conversation. - The magnifier searches customer names and message text. - Archived conversations only show when you filter by the **Archived** status. ![The conversation list, an open conversation and the details panel.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794742133306-01-conversations.png) ## Reply to a customer 1. Select a conversation in the list. 2. If nobody is assigned yet, select **Join** at the top. The chat is assigned to you, and the customer sees that you joined. 3. Type your reply in the box at the bottom. 4. Press Enter to send it. Shift+Enter starts a new line. ![2 Join. 3 Type your reply here.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794742135901-02-reply.png) To add a file, select the picture icon (**Upload Image**) or the paperclip (**Upload Document**, PDF only). You can send one file with each message, up to 10 MB. Point at a message to reply to it directly. You can also edit or delete your own messages, and the customer sees the change. > **Tip:** While Quanta is answering a chat, the message box is replaced by a bar that says "Quanta is answering this chat." Select **Take over** in that bar to answer it yourself. [Choose who answers first: Quanta or your team](/rectify/help/a/30-choose-who-answers-first) explains how chats move from Quanta to your team. ## Let Quanta help you reply Type **/** at the start of the message box and pick what you need: - **Draft a reply:** Quanta answers the customer's latest message for you to check. - **Summarize conversation:** the key points so far. - **Find related feedback:** feedback, requests and earlier chats from this person. - **Analyze attachments:** screenshots, session replays and documents from this person's feedback. You can also type any question after the **/** and press Enter. Quanta's answer opens above the message box. Select **Insert into reply** to use it, or **Copy**. Nothing reaches the customer until you send it. ![The Quanta commands in the message box.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106171724-03-quanta.png) To polish what you wrote, select at least 10 characters of it and pick **Enhance message**, **Fix grammar** or **Enhance and fix grammar**. The **Quanta** button at the top of the right-hand panel opens a longer chat with Quanta about this conversation. ## Mention a teammate or link feedback - Type **@** and pick a teammate to bring them in. They get an alert with a link to the conversation. - Type **#** and pick a feedback item to link it. It shows the customer's own feedback first, and you can type to search. You can link up to 5 items in one message. > **Warning:** A mention or a linked item is part of your reply, so the customer sees it too. The customer sees a linked item as a card with its title. Anything only your team should read belongs in the conversation's notes. ## Keep notes and details in the side panel The panel on the right shows who you're talking to: their name and email, and **View full profile** when they're one of your contacts. Below that: - **Quick Actions:** set the **Priority**: **Urgent**, **High**, **Medium**, **Low** or **None**. - **Conversation Log:** when the chat started, its status, priority and assignee. - **Guest Specifications:** the page the customer wrote from and their first contact. - **Past Feed:** earlier conversations with the same customer. - **Notes:** a private note for your team. Type it and select **Save Note**. Customers never see notes. ![Quick Actions and Notes open in the side panel.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106173356-04-details.png) ## Answer a chat from Discord A chat from your Discord server has the Discord mark next to it in the list and next to the person's name. Point at the mark to see **Discord · Private thread** or **Discord · Direct message**. You answer it like any other chat. A few things are different: - Above the message box, a line says where your reply goes, for example "Goes to Noah Bennett in Discord, in a private thread" or "Goes to Noah Bennett in Discord, by direct message". - Your reply shows in Discord with your name. If you edit or delete it in Rectify, it changes in Discord too. - **Join**, **Done** and **Reopen** post the same short notes in Discord as in the widget, like "Conversation marked as done". - Files you attach arrive in Discord as attachments, right after your message, so images show in the chat. A file too big for Discord arrives as a link instead. - Under the person's name, the side panel says **Discord member** instead of an email. The **Discord** section at the top of the side panel shows the **Server**, **Where** the chat happens, the **Member** and, when a moderator moved their message to support, who did it under **Moved by**. For a private thread, **Open in Discord** opens it. ![A chat from Discord, where the reply goes, and the Discord section.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794938313614-05-discord-chat.png) ### When Discord can no longer take replies If Rectify can't reach the person in Discord any more, a bar at the top of the chat says why: | **The bar says** | **What happened** | | --- | --- | | "Rectify is no longer in this Discord server." | Someone removed the Rectify app from your server. | | "The thread was deleted in Discord." | The private thread is gone. | | "This person is no longer in the server." | They left the server or were removed from it. | | "This person turned off direct messages." | They don't accept direct messages from the server any more. | | "Rectify can no longer reach this chat in Discord." | Rectify lost access to the thread or direct message, for example after a permission change. | | "This person's direct messages now go to a newer chat." | They started a newer chat by direct message, and their messages go there now. | The message box then says "This chat can no longer receive replies in Discord. Add a note for your team instead.", and you can't send. A reply that didn't reach Discord shows **Not sent to Discord**. Everything stays in Rectify, and the side panel says "Replies stay in Rectify." If the person asks again with /support, a new chat starts. ![A chat Discord can no longer reach, with Not sent to Discord.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794938320611-06-discord-cannot-reply.png) ## Close or archive a conversation - **Done** closes the conversation. The customer sees that it's closed and can download a copy of the chat. Select **Reopen** to open it again. - **Archive** takes it out of the list without telling the customer. Filter by the **Archived** status to find it, then select **Unarchive** to bring it back. - The bin icon deletes the conversation and everything in it. You'll be asked to confirm, and it can't be undone. To stop customers replying to a closed conversation, switch on **Lock closed conversations** in your widget settings. [Set up widget chat, the live support channel](/rectify/help/a/29-set-up-widget-chat) shows where. ## Start a chat yourself You can invite a customer to a chat, for example to follow up on a question they emailed you. 1. Select **New Chat** at the top of Conversations. 2. Enter the customer's name and email under **Guest**. 3. Write the **Message** they read first, in the email and in the chat. 4. Under **Chat link**, enter the page on your site where the widget runs. 5. Select **Send invite**. The customer gets an email with a secure link that opens the chat on that page. The chat is assigned to you. ## Get alerts for new chats Each person chooses their own alerts. Select your name at the bottom of the sidebar, then **Notifications**, and check these under **Alerts**: - **Support Session Started:** a customer started a chat, with Quanta or your team. - **Human Support Requested:** a customer asked Quanta for your team. - **Support Inbox Message:** a customer wrote in a conversation that's yours, or in one nobody is assigned to. - **Support Chat Assigned:** a conversation was assigned to you. - **Mentioned in Conversation:** a teammate mentioned you with **@**. [Your profile and notification settings](/rectify/help/a/11-profile-and-notification-settings) explains push and email alerts. ## Replies on the Idea plan On the free Idea plan, your team can send 10 replies a month. Every message your team sends counts, and so does every **New Chat** invite. Quanta's answers don't count. The allowance starts again at the beginning of each month. To see what's used, open **Organization settings**, then **Billing**, and look for **Support Inbox**. All paid plans have unlimited replies. ## Troubleshooting ### I can't type a reply Quanta is still answering this chat. Select **Take over** in the bar at the bottom of the chat to answer it yourself. ### It says "In order to continue using this feature, please upgrade your plan." Your team has used this month's 10 replies on the Idea plan. Select **Upgrade Now**, or wait until next month. [Compare plans and what each one includes](/rectify/help/a/13-compare-plans) lists the limits. ### I can't send a reply in a chat from Discord Rectify can no longer reach the person in Discord. The bar at the top of the chat says why. Keep a note for your team in **Notes** instead. ### Done, Archive or Priority is greyed out They're for Owners and Admins. Ask one of them to change it, or to change your role. ### It says "File size exceeds the limit of 10MB." Pick a smaller file, or send a link to it instead. ## Read next - [Choose who answers first: Quanta or your team](/rectify/help/a/30-choose-who-answers-first) - [Set up widget chat, the live support channel](/rectify/help/a/29-set-up-widget-chat) - [Set up support chat in Discord](/rectify/help/a/131-set-up-support-chat-in-discord) - [Track support performance](/rectify/help/a/33-track-support-performance) --- # Track support performance Collection: Inbox URL: https://app.rectify.so/rectify/help/a/33-track-support-performance See how many chats you get, how many Quanta resolves on its own and how fast customers get a reply, by asking Quanta. > **Note:** **Before you start.** The support overview comes from Quanta, so your organization needs an AI provider or Rectify credits. Everyone on your team can ask for it. ## Ask Quanta for the support overview 1. Select **Quanta** at the top of the sidebar. 2. Ask for the support overview, for example "Show me the support overview: total conversations, AI resolution and response time." 3. Quanta answers with the key numbers. Select **Expand** to open the full **Support Overview** next to the chat. ![Quanta's answer, with Expand.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106176038-01-ask.png) To narrow it down, name a period in your question, for example "this month". To come back to an overview later, open the chat from **History** and select **Expand** again. The overview counts chats from widget chat and from Discord together. ![The Support Overview.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106177868-02-canvas.png) ## What the numbers mean | **Number** | **What it counts** | | --- | --- | | **Total Conversations** | Conversations started in the period you asked about, or all of them if you didn't name one. It includes ones only Quanta answered. **active now** is how many of them are still open. | | **AI Resolution** | The share of conversations that never reached your team. | | **Avg Response** | The average time from a customer's message to the next reply, from Quanta or your team. Quanta's replies count as instant, so the more Quanta answers, the lower it gets. | | **Human Escalation** | The share of conversations that reached your team: handovers, chats you took over, and every chat started while **Team only** is on. | | **Conversation Status** | How many conversations are open, done or archived. | | **Priority Breakdown** | How many conversations have each priority. | | **Conversation Trend** | New conversations per day, for up to 14 of the days that had any. | ## Count the last 30 days Open **Inbox**, then **Channels**. The **Widget chat** row shows how many conversations started in the last 30 days, next to who answers. If you've [set up support chat in Discord](/rectify/help/a/131-set-up-support-chat-in-discord), the **Discord** row shows the same for chats from your server. ## See what's waiting each morning The Quanta page opens with a short briefing of what needs you. When a customer has written in a conversation handed to your team and nobody on your team has opened it since, the briefing says how many chats are waiting for a reply. - Select **Conversations** to go straight to them. - Select **Summarise** to have Quanta sum them up for you. ![Chats waiting for a reply, in the Quanta briefing.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106179540-03-briefing.png) Opening a conversation in **Conversations** takes it off the count. ## Troubleshooting ### Quanta doesn't show the overview Ask for it by name, for example "Show me the support overview". ### It says "No AI provider is configured" Your organization has no AI key connected and no Rectify credits left. Ask an Owner or Admin to connect a provider under **Organization settings**, **AI providers**. ## Read next - [Answer chats in the support inbox](/rectify/help/a/32-answer-chats-in-the-support-inbox) - [Meet Quanta, your AI teammate](/rectify/help/a/7-meet-quanta) --- # What your users see in the widget Collection: Widget URL: https://app.rectify.so/rectify/help/a/18-what-your-users-see-in-the-widget A tour of the widget from your visitor's side, from the launcher and home screen to each tab and how it looks on a phone. Once the script is on your site, every visitor gets a launcher in the corner of the page. Selecting it opens the widget, where they can report a bug, share an idea, chat with you, read your changelog and roadmap, and search your help articles. The preview on the Widget page shows the same widget with your current settings. Open **Publish**, then **Widget**, to see it. ![1 Greeting. 2 Home menu cards. 3 Tabs. 4 Launcher.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106074249-01-home.png) ## The launcher The launcher is the button that opens and closes the widget. It sits bottom right unless you move it. Visitors can drag it somewhere else on the page, and their browser remembers the spot until you change the launcher's **Position**. Two small signs show on it: - A dot when one of your team or Quanta has replied in a conversation. New replies also play a sound and add the number of unread replies to the browser tab's title. - A red dot when there's a changelog entry the visitor hasn't seen yet. ## The home screen The widget opens on the home screen. If you've turned **Home** off, it opens on the first tab that is on instead, and your script can also open it on a tab of your choice. The home screen has: - **The header** with your logo, the widget title and a close button. If you show your team on the home screen, up to three of their photos appear here too. - **The greeting**, for example "Hi Jane" with a wave, and a welcome line under it. The visitor's name only appears when your site tells the widget who they are. - **The home menu cards.** By default these are **Report a Bug**, **Share an Idea** and **General Feedback**. Each opens its own short form. You can also add **Share Your Experience**, a link to your own contact page, a card that opens your help articles, and **Chat with us**, the Support card, which starts a conversation with you. If no card is on, visitors see only the greeting. - **Powered by Rectify** at the bottom, unless you've hidden it. - **The tabs** along the bottom, when two or more are on. ## The tabs | **Tab** | **What visitors do there** | | --- | --- | | **Home** | Pick a card to send feedback, open a link or start a chat. | | **Support** | Start a conversation and see past ones. Quanta or your team answers, depending on your Support settings. The first time, visitors enter their name and email and select **Continue**. | | **Changelog** | Read what you've shipped, filter by label and open an entry. Signed-in visitors with an email can select **Subscribe** to get new releases by email. | | **Roadmap** | See your public roadmap under **Roadmap**, and browse, vote on and post ideas under **Requests**. | | **Help** | Search your help articles, open them in the widget and, if it's on, ask Quanta a question. | Home, Support, Changelog and Roadmap are on when you start. Help is off until you turn it on. [Choose the widget's tabs](/rectify/help/a/20-choose-the-widgets-tabs) shows how to change them. The tab bar only shows when two or more tabs are on. Two or three tabs sit together in the middle, and four or more spread across it. The bar is also hidden in the **Home and support** and **Support only** layouts, see [Choose the widget's layout](/rectify/help/a/126-choose-the-widgets-layout). Without the bar, the Support, Changelog, Roadmap and Help screens show a back arrow to Home. ## Popups and what's new The widget can also speak first. A popup message can appear beside the launcher before anyone opens it, see [Show popup messages](/rectify/help/a/22-show-popup-messages). If you turn on **Open when something shipped** for the Changelog tab, returning visitors see your newest entry in a **What's new** card with **Later** and **Read more**. ## Signed-in visitors and anonymous visitors When your site tells the widget who is signed in, the widget greets them by name and fills in their name and email in the feedback forms and in Support. They also show up in your contacts. To vote, post and comment as themselves in the Roadmap, Changelog and Help tabs, they need to be signed in with a signature from your server. Without it, they use those tabs anonymously, as far as your portal settings allow. Where your portal only allows signed-in members, the widget says so, for example "Only signed-in members can vote here." [Sign in verified users](/rectify/help/a/23-sign-in-verified-users) explains both steps. ## On a phone On a screen 640 pixels wide or narrower, the widget fills the whole screen when it's open. On larger screens it opens as a panel next to the launcher. In the preview, select the phone icon at the top to see the phone layout. ![The phone preview of the widget.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106076286-02-phone.png) ## Powered by Rectify The widget shows **Powered by Rectify** at the bottom of every screen. On the Launch, Accelerate and Enterprise plans you can hide it under **Look**, in **Powered by**. See [Compare plans and what each one includes](/rectify/help/a/13-compare-plans). ## Read next - [Style the launcher and the widget](/rectify/help/a/19-style-the-launcher-and-the-widget) - [Choose the widget's layout](/rectify/help/a/126-choose-the-widgets-layout) - [Collect feedback and bug reports in the widget](/rectify/help/a/21-collect-feedback-and-bug-reports) - [The widget doesn't show: what to check](/rectify/help/a/24-the-widget-does-not-show) --- # Style the launcher and the widget Collection: Widget URL: https://app.rectify.so/rectify/help/a/19-style-the-launcher-and-the-widget Change the widget's header, greeting, background, colours and corners, and choose how the launcher looks and where it sits. > **Note:** **Before you start.** Owners, Admins and Members can change the widget. Hiding **Powered by Rectify** needs the Launch plan or higher. Everything about how the widget looks is under **Look** on the Widget page. The preview on the left changes as you go, and nothing reaches your site until you save. ## Change the look 1. In your project, open **Publish**, then **Widget**. **Look** opens first. 2. Change a setting, for example the **Title**. The preview updates straight away. To find a setting fast, click that part of the preview. 3. Select **Save** in the bar at the bottom. ![2 Title, under Header and greeting. 3 Save.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106078866-01-change-and-save.png) The bar also has **Discard** to throw away your changes, and undo and redo buttons. Ctrl or Cmd Z undoes too. Select **Guide** at the top of the page to show a line of help under every setting. ## Header and greeting | **Setting** | **What it does** | | --- | --- | | **Logo** | Shown beside the title. **Upload** your own (JPEG, PNG or GIF up to 10 MB), select **Use project logo** or **Use default**, or remove it. | | **Title** | The name next to the logo. It starts as "Send Feedback". | | **Greeting** | The first big line. The two boxes wrap around the visitor's name, "Hi" and a wave to start. | | **Show the visitor's name** | Puts the visitor's name between the two greeting boxes when your site tells the widget who they are. | | **Welcome message** | The line under the greeting. It starts as "How can we help you today?". | ## Background The background sits behind the header and greeting. Pick a **Style**: - **Solid**: one colour. - **Gradient**: a **Start** and **End** colour, a **Direction**, the **Intensity** of the blend and the **Midpoint** where the colours meet. **Edge** sets whether the bottom fades into the panel or stops sharply. This is the style you start with. - **Animated**: a moving **Pattern** (Ripple, Waves, Aurora, Flow, Sparkle or Bubbles) in a **Palette** of five colours. Turn **Animate** off to keep it still. - **Image**: your own picture, with **Blur** from 0 to 20 px. Select **Use default** for ours. **Height** sets how far down the panel the background reaches, from 30% to 100%. It always covers the greeting. **Height** isn't available for **Animated**. ## Colours and corners ![Colors and corners, with the preview beside it.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106080503-02-colors.png) | **Setting** | **What it colours** | | --- | --- | | **Primary** | Buttons, links, the active tab and the header of every screen after Home. | | **Text** | The titles and descriptions on the home menu cards, and the tabs. | | **Background** | The home menu cards and the tab bar. | | **Corner radius** | How round the widget and its cards are, up to 20 px. | | **Opens** | Where the panel appears: **Around the launcher** or in the **Center** of the page. | Your project's brand colour is used for **Primary**, the background and the launcher icon when the project is created. ## The launcher ![1 Pill, a launcher style. 2 Label, the text on it.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794724957536-03-launcher.png) | **Setting** | **What it does** | | --- | --- | | **Style** | **Icon button** (a round button), **Text tab** (a tab on the edge of the page) or **Pill** (an icon with a word). | | **Label** | The text on a **Text tab** or **Pill**, up to 24 characters. It starts as "Feedback". | | **Position** | Middle left, middle right, bottom left or bottom right. A **Pill** always sits in a bottom corner. | | **On click** | What opens when someone clicks the launcher: a tab, or a feedback form such as **Share an Idea**. Until you change it, a click opens the widget on its opening tab. | | **Size** | **Small**, **Default** or **Large**. Not for a **Text tab**. | | **Distance from the edge** | 0 to 64 px between the button and the screen edge. Not for a **Text tab**. | | **Corner radius** | From square corners (0) to fully round (32 px). | | **Text only** | For a **Text tab**: drop the icon and show just the label. | | **Icon** | One of five presets, or select **More icons** to search for any icon. | | **Text and icon color** | The colour of the icon and label on the button. | | **Button color** | The colour behind the icon or label. | **Hide the launcher** is for opening the widget from your own button. [The widget doesn't show: what to check](/rectify/help/a/24-the-widget-does-not-show) covers what happens when it's on. These settings apply on every site that runs your snippet. To give one site, or some of its pages, a different launcher, see [Give a site or page its own launcher](/rectify/help/a/127-give-a-site-or-page-its-own-launcher). ## Powered by Rectify Under **Powered by**, choose **Keep** or **Hide** for **Powered by Rectify**. On a plan below Launch, choosing **Hide** opens the upgrade screen instead. See [Compare plans and what each one includes](/rectify/help/a/13-compare-plans). ## Check it worked After you select **Save**, open your site in a new tab and refresh it. The launcher and the widget show your new look. ## Troubleshooting ### I can't pick a middle position The **Pill** launcher only sits in a bottom corner, so the middle positions are greyed out. Choose **Icon button** or **Text tab** to use them. ### It says "Pick an image under 10 MB" Logos and background images can be up to 10 MB, in JPEG, PNG or GIF. Make the image smaller and upload it again. ### The launcher sits somewhere else on my site You, or a visitor, dragged it there. The browser remembers the spot until you change the **Position** setting. Clear the site's data in your browser to put it back. ### It says "Leave without saving?" You changed something and haven't saved. Select **Keep editing**, then **Save**, or select **Leave** to drop your changes. ## Read next - [Choose the widget's tabs](/rectify/help/a/20-choose-the-widgets-tabs) - [What your users see in the widget](/rectify/help/a/18-what-your-users-see-in-the-widget) --- # Give a site or page its own launcher Collection: Widget URL: https://app.rectify.so/rectify/help/a/127-give-a-site-or-page-its-own-launcher Use one snippet on several sites and give each site, or some of its pages, its own launcher and its own choice of what a click opens. > **Note:** **Before you start.** Owners, Admins and Members can change the widget. Every plan can give sites and pages their own launcher. Up to 20 sites can have settings of their own, each with up to 20 page settings. When the same snippet runs on more than one site, for example your marketing site and your app, every site shows the launcher you set under **Look**. You can give one site, or some pages on it, a launcher of its own: show or hide it, move it, restyle it, or change what a click opens. A site keeps only the settings you change for it and follows your default launcher for the rest. Pages work the same way inside their site. When more than one setting covers a page, the most specific one wins: the page, then the site, then the default. ## Give a site its own launcher 1. In your project, open **Publish**, then **Widget**. **Look** opens first. 2. Scroll to **Sites**, under the launcher settings. Every site the widget has loaded on is listed, with when it was last seen. 3. Select **Customize** next to the site. ![2 Sites. 3 Customize.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794724922577-01-sites.png) 4. Change what you need. **Launcher** shows or hides it, **Position** moves it and **On click** picks what opens. Open **Look** for the style, label, icon and colours. The sentence at the top says what the launcher on that site does. ![4 On click, set to the Share an Idea form. The sentence above it follows your changes.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794724924902-02-site-editor.png) 5. Select **Save** in the bar at the bottom. A dot marks every setting that differs from your default launcher, and **Reset** puts the site back in line with it. Select **All sites** at the top of the panel to go back to the list. ## Give some pages their own launcher 1. Open the site, as above. 2. Under **Pages**, select **Add a page**. 3. In **Only on these pages**, list the pages, with commas between them, or select one of the **Pages people visit on this site**. ![3 Only on these pages, here /pricing, picked from the pages people visit on that site.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794724926899-03-pages.png) 4. Set the launcher for those pages. For example, select **Hide** next to **Launcher** to show no launcher there. 5. Select **Save**. How the list matches pages: - `/pricing` covers that page only. - `*` stays inside one folder: `/docs/*` covers `/docs/setup`, not `/docs/setup/install`. - `**` goes across folders: `/docs/**` covers every page under `/docs`. - Anything after a `?` in the address is ignored, unless your list has a `?` too. - If two page settings cover the same page, the first one in the list wins. ## Choose what a click opens **On click** is in every site and page setting, and under **Look** for your default launcher too. Pick a tab under **Open a tab**, or a form under **Open a form** to take visitors straight to it, such as **Share an Idea** or **Report a Bug**. Only the tabs and forms that are switched on are listed. Until you change it, a click opens the widget as before, on its opening tab. If you later switch off the tab or form you picked, a click simply opens the widget, and the setting shows **(off)** after its name. ## Add a site by hand A site shows up on its own the first time the widget loads there. To set one up before that: 1. Under **Sites**, select **Add a site**. 2. Enter the **Site address**, for example `app.yoursite.com`, and select **Add a site**. 3. Change its launcher, then select **Save**. ## Preview a site The address bar above the preview picks the site. Select it, then pick **All sites** to see your default launcher, or a site or one of its page settings. With a site picked, click the launcher in the preview to see what it opens. ![The site picker in the address bar above the preview.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794724930217-04-picker.png) > **Tip:** Quanta can do this too. Ask it, for example, "Hide the launcher on the login page of `app.yoursite.com`". It shows you the change and saves it only after you select **Confirm**. ## Remove a site's settings Open the site, select **Remove** at the top of the panel, then select **Save**. To remove one page setting, open it, select **Delete**, then **Save**. The site or page follows the level above again. ## Check it worked After you select **Save**, open the site in a new tab and refresh it. The launcher shows that site's settings. Go to one of the pages you listed to see the page setting. ## Troubleshooting ### My site isn't in the list A site appears the first time the widget loads there. Open a page of that site, then refresh the Widget page. You can also add it by hand with **Add a site**. A site the widget hasn't loaded on for 90 days drops off the list, unless it has settings of its own. ### The launcher on my site didn't change Settings load each time a page loads, so refresh the page. Check that the address under **Sites** matches the one in your browser. `www.` is dropped, but `app.yoursite.com` and `yoursite.com` are two different sites. ### A page setting doesn't apply Check the list under **Only on these pages**. `*` never crosses a `/`, so use `**` for pages further down, like `/docs/**`. If two page settings cover the page, the first one in the list wins. When the list is empty, the note "List at least one page, or this setting applies nowhere." shows under it. ### It says "Use an address like app.yoursite.com" Enter just the site's address, like `app.yoursite.com` or `yoursite.com`. A path after it is dropped. ### I can't pick a middle position The **Pill** launcher only sits in a bottom corner, so the middle positions are greyed out. Choose **Icon button** or **Text tab** under **Look** to use them. ## Read next - [Style the launcher and the widget](/rectify/help/a/19-style-the-launcher-and-the-widget) - [The widget doesn't show: what to check](/rectify/help/a/24-the-widget-does-not-show) --- # Choose the widget's tabs Collection: Widget URL: https://app.rectify.so/rectify/help/a/20-choose-the-widgets-tabs Turn the Support, Changelog, Roadmap and Help tabs on or off, put them in order, and rename them or change their icons. > **Note:** **Before you start.** Owners, Admins and Members can change the tabs. Every tab is available on every plan. The tabs sit along the bottom of the widget. You start with **Home**, **Support**, **Changelog** and **Roadmap** switched on, and **Help** switched off. In a widget set up a while ago, **Support** may be called **Messages**. It works the same way. ## Turn tabs on, off and in order 1. In your project, open **Publish**, then **Widget**. **Look** opens first. 2. Scroll down to **Bottom navigation**. 3. Use the switch next to a tab to turn it on or off. **Home** can be turned off too. The last tab that is on can't be turned off. 4. To change the order, drag a tab by the handle on its left. ![3 The switch for Help. 4 The drag handle. The preview shows the tabs as visitors see them.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793391236069-01-bottom-navigation.png) 5. To rename a tab or change its icon, select its name. Select **Change** next to **Icon** to pick a new icon, and type a new **Label**. ![5 The Changelog tab, opened.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793391237453-02-changelog-tab.png) 6. Select **Save** in the bar at the bottom. The label you choose is also the title at the top of that tab in the widget. The bar changes with the number of tabs. With one tab on, there's no bar. Two or three tabs sit together in the middle of the bar, and four or more spread across it. If you turn **Home** off, a line under the tabs says where the widget opens instead, for example "Home is off, so the widget opens on Support." ## Open the changelog when something ships Open the **Changelog** tab in the list to see three more settings: | **Setting** | **What it does** | | --- | --- | | **Open when something shipped** | A returning visitor with entries they haven't seen gets the newest one in a **What's new** card, once per visit. Off, they just see a dot on the tab. | | **Skip first-time visitors** | On a first visit, everything published so far counts as seen, so new visitors aren't greeted with old news. On when you start. | | **Only recent entries** | Only entries from the **Last 7 days**, **Last 30 days** or **Last 90 days** open on their own. Older ones still show in the tab. | ## Hide the tab bar The bar has no switch of its own. To hide it, pick **Home and support** or **Support only** under **Home menu**, **Layout**. [Choose the widget's layout](/rectify/help/a/126-choose-the-widgets-layout) shows what each layout does. While the bar is off, **Bottom navigation** shows a line such as "The bar is off in the Support only layout." Select **Change the layout** to go back to the tiles. ## What each tab shows - **Home** shows your home menu cards. Change them under **Home menu**, see [Collect feedback and bug reports in the widget](/rectify/help/a/21-collect-feedback-and-bug-reports). - **Support** is where visitors chat with Quanta or your team. Its settings are under **Support**. - **Changelog**, **Roadmap** and **Help** show your portal's changelog, roadmaps, request boards and help articles. Which boards visitors can see, who can vote or post, and who can read the changelog are set in **Publish**, **Portal**. **Help** shows your published help articles. ## Open the widget on a tab Without a setting in your script, the widget opens on **Home**, or on the first tab that is on when **Home** is off. Your script can open the widget on another tab, and that setting always wins. Under **Install**, **Start on a tab or hide the launcher** shows the setting to add to your script. Use `home`, `support`, `changelog`, `roadmap` or `help`. ## Check it worked The preview on the left shows the tab bar as you change it. After you select **Save**, refresh your site and open the widget. ## Troubleshooting ### The tab bar disappeared The bar only shows with two or more tabs on, so check that more than one is switched on. It's also off in the **Home and support** and **Support only** layouts. To bring it back, open **Home menu** and select **Home and tabs** under **Layout**. ### I can't turn off a tab The widget needs at least one tab, so the switch of the last tab that is on can't be turned off. Turn another tab on first. ### The Help tab shows "No articles yet" The tab only shows published articles. Publish some articles in your Help Center first. ### Visitors see "This portal is private" Your portal only lets some people in. Visitors who aren't signed in see this in the Changelog, Roadmap and Help tabs. [Sign in verified users](/rectify/help/a/23-sign-in-verified-users) shows how to sign them in from your site. ## Read next - [Choose the widget's layout](/rectify/help/a/126-choose-the-widgets-layout) - [What your users see in the widget](/rectify/help/a/18-what-your-users-see-in-the-widget) - [Style the launcher and the widget](/rectify/help/a/19-style-the-launcher-and-the-widget) --- # Choose the widget's layout Collection: Widget URL: https://app.rectify.so/rectify/help/a/126-choose-the-widgets-layout Pick Home and tabs, Home and support or Support only to set what visitors see when they open the widget, including a support-only widget. > **Note:** **Before you start.** Owners, Admins and Members can change the layout. Every layout is available on every plan. The layout decides what visitors see when they open the widget: your home cards with a tab bar, a chat card at the top of your home cards, or a chat and nothing else. | **Layout** | **What visitors see** | | --- | --- | | **Home and tabs** | Home with your cards, and a bar for the tabs switched on in **Look**. This is how the widget starts. | | **Home and support** | Home with the **Support** card first and your other cards below. No bar. | | **Support only** | A support screen under your header and greeting. No bar, no other cards. | ## Pick a layout 1. In your project, open **Publish**, then **Widget**, and select **Home menu**. 2. Under **Layout**, select **Home and tabs**, **Home and support** or **Support only**. The preview on the left changes straight away, and the line under the tiles describes the layout you picked. ![1 Home menu. 2 The three layouts.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793391220293-01-layout.png) 3. Select **Save** in the bar at the bottom. Picking a layout changes these settings for you: - **Home and support** and **Support only** turn on the **Home** and **Support** tabs and hide the bar. - **Support only** turns off every other Home card. - **Home and support** puts the **Support** card first. If no other card is on, it turns on **Report a Bug**, **Share an Idea** and **General Feedback**. - **Home and tabs** shows the bar again and leaves your tab switches as they were. Your other tabs keep their switches in **Look**, so they come back when you return to **Home and tabs**. ## The Support card The **Support** card is the card that starts a chat. Visitors see it as **Chat with us**, with "Ask us anything, we reply here" under it and a message icon. Selecting it starts a conversation, the same way the start button in the **Support** tab does. Quanta or your team answers, as set under **Support**. It's off when you start, and the two support layouts switch it on. You can also switch it on yourself in **Home and tabs**: find **Support** in the **Home menu** list and use its switch. Select its name to change the **Title**, **Description**, **Icon** and **Icon color**. The card stays hidden while the **Support** tab is off. In a widget set up a while ago, that tab may be called **Messages**. It works the same way. ## What visitors see ### Support only The first time, the card asks for a name and an email and shows your start button, with the label set under **Support**, **Start button**. The default is **Start a conversation**. Filling it in starts the chat. ![Support only, as a first-time visitor sees it.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793391221665-02-support-only.png) When they come back, the card is a single button that starts a new conversation. Under it, **Your conversations** opens their earlier chats and shows **New** when a reply is waiting. ### Home and support The same card sits first, above your other cards. The first time, selecting it opens **Support**, where visitors enter their name and email before the chat starts. When they come back, **Your conversations** sits under the card. ![Home and support, as a returning visitor sees it.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793391223195-03-home-and-support.png) ### Without the bar In both support layouts, the **Support**, **Changelog**, **Roadmap** and **Help** screens show a back arrow to **Home**, so visitors can always get back to your cards. ## Go back to tabs 1. Open **Publish**, then **Widget**, and select **Home menu**. 2. Under **Layout**, select **Home and tabs**. 3. Select **Save**. The bar comes back with the tabs switched on in **Look**. The **Support** card stays on, in the same place in the list. Switch it off under **Home menu** if you don't want it. While the bar is off, **Look**, **Bottom navigation** shows a line such as "The bar is off in the Support only layout." Select **Change the layout** there to go straight to the tiles. ## Check it worked The preview on the left shows the layout as you pick it. After you select **Save**, refresh your site and open the widget. To see the first-visit card, open your site in a private window. ## Troubleshooting ### The line under the tiles says "Your settings don't match a layout right now" The tabs or cards were changed by hand while the bar is hidden, for example **Home** or the **Support** card was switched off. Select the layout you want and the settings are set up for it. ### Visitors don't see the Support card The card stays hidden while the **Support** tab is off. Under **Home menu**, the note "The Support card stays hidden while the Support tab is off." shows when this happens. Turn **Support** on in **Look**, under **Bottom navigation**, or pick one of the support layouts. ### The widget shows only the greeting No Home cards are on. Under **Home menu**, the note "No cards are on, so visitors see only the greeting." shows when this happens. Switch on a card, or pick a layout. ## Read next - [Set up widget chat, the live support channel](/rectify/help/a/29-set-up-widget-chat) - [Choose the widget's tabs](/rectify/help/a/20-choose-the-widgets-tabs) - [What your users see in the widget](/rectify/help/a/18-what-your-users-see-in-the-widget) --- # Collect feedback and bug reports in the widget Collection: Widget URL: https://app.rectify.so/rectify/help/a/21-collect-feedback-and-bug-reports Choose which feedback forms visitors see, edit their fields and thank-you screen, and decide what bug reports record. > **Note:** **Before you start.** Owners, Admins and Members can change the forms. Session replays count towards a monthly limit on your plan, and console, network and action logs need the Build plan or higher. Each card on the widget's home screen opens its own form. Three are on when you start: **Report a Bug**, **Share an Idea** and **General Feedback**. A fourth, **Share Your Experience**, is there for testimonials but starts switched off. ## Choose which forms show 1. In your project, open **Publish**, then **Widget**, and select **Home menu**. 2. Use the switch next to a card to show or hide it. In this list the cards have their own names, for example **Feedback: Bug** for **Report a Bug**. 3. To change a card's text, select its name and edit the **Title** and **Description**. You can also pick its **Icon** and **Icon color**. 4. Drag a card by the handle on its left to change the order. 5. Select **Save** in the bar at the bottom. The same list has **Custom Link**, a card that opens one of your own pages in a new tab, and **Help Center**, a card that opens your help articles. It also has **Support**, a card that starts a chat with you. It starts switched off and only shows while the **Support** tab is on. [Choose the widget's layout](/rectify/help/a/126-choose-the-widgets-layout) explains how to use it. ## Edit a form 1. Open **Publish**, then **Widget**, and select **Home menu**. 2. Select the pencil button next to the card you want to change. ![1 Home menu. 2 The pencil button for Feedback: Bug.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106089715-01-edit-form.png) 3. Under **Fields**, use the switch next to a field to show or hide it. Drag a field by its handle to change the order. 4. Select a field's name to change its **Placeholder**, the hint inside the empty field, and turn **Required** on or off. For **Rating**, pick the **Scale**: **Stars**, **Hearts**, **Faces** or **Numbers**. 5. Under **Attachments**, choose what people can add: **Screenshot**, **Screen recording** and **File attachment**. ![3 The switch for Priority. 4 Open a field. 5 The attachment switches.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106091363-02-fields.png) 6. Under **Submit button**, change the **Label**, up to 40 characters. 7. Select **Success** at the top to change the thank-you screen. Turn **Show an icon** on or off, pick an **Animation**, and write a **Heading** and a **Message**. ![The thank-you screen settings, with the preview on the left.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106092996-03-success.png) 8. Select **Save** in the bar at the bottom. When you start, every form asks for an **Email**, a **Title** and a **Description**, which are required, and a **Category**, which is optional. **Rating**, **Name**, **Priority** and **Custom Field** are switched off. ### Add a checkbox or a line of text Switch on **Custom Field**, select its name and choose a **Kind**: - **Checkbox**: a box with your text beside it, for example to agree to your terms. - **Disclaimer text**: a line of text with nothing to fill in. Write the **Text**, up to 500 characters. Links work in Markdown, like `[terms](https://example.com)`. Turn on **Required** to make visitors tick the checkbox before they can send. ## What visitors fill in Visitors open a card, fill in the fields you've switched on and select the submit button. If your site tells the widget who they are, their name and email are already filled in. - **Screenshot** lets them capture the page they're on and draw on it before adding it. They can add up to 10. - **Screen recording** records their screen with Loom. A report can have screenshots or a recording, not both. - **File attachment** adds one file, up to 10 MB. After they send it, they see the thank-you screen you set up. ## Record what happened before a bug For **Report a Bug**, the widget can attach a replay of the visit and technical logs, so you can see what went wrong. 1. Open **Publish**, then **Widget**, and select **Privacy**. 2. Turn **Record sessions** on for a visual replay of the visit, attached to each bug report. 3. Turn **Capture technical logs** on for console logs, network requests and user actions. ![2 Record sessions. 3 Capture technical logs.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106094626-04-privacy.png) 4. Under **Masking**, choose what never leaves the visitor's browser: **Mask all text**, **Mask all inputs**, or the field types under **Always mask these inputs**. Passwords are always masked. You can also hide parts of your page by CSS class with **Mask by class**, **Block by class** and **Ignore by class**. 5. Select **Save**. Both start switched on. Only bug reports carry a replay and logs. Ideas and general feedback don't. | **Plan** | **Session replays a month** | | --- | --- | | Idea | 10 | | Build | 100 | | Launch | 1,000 | | Accelerate | 5,000 | | Enterprise | Unlimited | When you reach your plan's limit, bug reports still arrive, without a replay. ## Where reports go Every report lands in **Inbox**, **Feedback**. Bug reports with a replay are also listed under **Inbox**, **Session replays**. ## Check it worked Open your site, open the widget and send a test report from the card you changed. It appears under **Inbox**, **Feedback**. ## Troubleshooting ### A visitor sees "Please rate your experience" **Rating** is required on that form and they didn't pick a rating. Make it optional if you don't need it. ### A bug report has no session replay Check that **Record sessions** is on under **Privacy**, and that the report came from **Report a Bug**. If your plan's monthly replays are used up, reports arrive without one. ### An attachment is missing from a report Files over 10 MB aren't attached. Ask the visitor for a smaller file. ### A visitor sees "Too many uploads. Please try again in a few minutes." The widget limits how many files can be uploaded from one network in 15 minutes. They can send the report again a little later. ## Read next - [Choose the widget's tabs](/rectify/help/a/20-choose-the-widgets-tabs) - [Compare plans and what each one includes](/rectify/help/a/13-compare-plans) --- # Show popup messages Collection: Widget URL: https://app.rectify.so/rectify/help/a/22-show-popup-messages Greet visitors with a short message beside the launcher, on the pages, devices and people you choose. > **Note:** **Before you start.** Owners, Admins and Members can add popup messages, on every plan. A project can have up to 20. A popup message is a short note that appears beside the launcher before anyone opens the widget, for example a hello on your pricing page. When a visitor selects it, the widget opens on **Support** so they can reply. ## Add a popup message 1. In your project, open **Publish**, then **Widget**, and select **Popups**. 2. Select **Add message**. A new message opens, switched on, with sample text. ![1 Popups. 2 Add message.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106097241-01-add-message.png) 3. Enter a **Name**. Only your team sees it. 4. Write the **Message**, up to 140 characters. The preview shows it beside the launcher as you type. 5. Choose who it's **From**: Quanta, a **Team member**, or **Nobody, just the message**. The table under these steps shows what each one means. 6. Optional: add up to two **Quick replies**, up to 30 characters each. Selecting one opens Support with it ready to send. 7. Choose how long it stays. Turn on **Stay until the visitor closes it**, or set **Stays on screen for** between 3 and 120 seconds. It starts at 8. ![3 Name. 4 Message. 5 From. 6 Quick replies. 7 Stays on screen for. The preview shows the message beside the launcher.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106098931-02-message.png) 8. Set who sees it, where and when, as described below, then select **Save** in the bar at the bottom. ## Who the message is from | **From** | **What visitors see** | **Who answers a reply** | | --- | --- | --- | | Quanta | Quanta's name and logo, or the ones you set on the **Support** tab. In the list it's called **AI assistant** until you give Quanta a name there. | Quanta | | **Team member** | The name and photo of the agent you pick. Only people you've added as agents on the **Support** tab are listed. | That person | | **Nobody, just the message** | Just the message. | Whoever your **Support** settings say | ## Choose who sees it Under **Who sees it**, pick an **Audience**: **Everyone**, **Known contacts** (visitors you've identified) or **Anonymous only**. To narrow it down further, select one or more segments under **Limit to segments**. Anonymous visitors are never in a segment, so don't combine the two. ## Choose where it shows ![The Who sees it and Where it shows settings.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106100759-03-where.png) | **Setting** | **What it does** | | --- | --- | | **Only on these pages** | Pages it can show on, separated by commas. Empty means every page. | | **Never on these pages** | Pages it never shows on. This wins over the list above. | | **Devices** | **Desktop**, **Tablet** or **Mobile**. None selected means all devices. | | **Visitors** | **Everyone**, **New visitors** or **Returning visitors**. New means their first visit to your site. | Pages are matched on the part of the address after your domain, including anything after a `?`: - `/pricing` matches only `/pricing`. - `*` matches anything within one part of the address. `/docs/*` matches `/docs/install` but not `/docs/widget/install`. - `**` matches across parts. `/docs/**` matches both. ## Choose when and how often ![The When and how often settings.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106102387-04-when.png) Under **Show it when**, pick a trigger. Select **Trigger** to add up to three, and the first one to happen shows the message. | **Trigger** | **When the message shows** | | --- | --- | | **Straight away** | As the page loads, or after the number of seconds you enter. | | **After a delay** | After the visitor has been on the page for the number of seconds you enter. New messages start at 5. | | **After scrolling** | Once the visitor scrolls down the percentage of the page you enter. | | **When leaving** | When the pointer moves up out of the page, towards the address bar or close button. | | **After frustration** | After rage clicks, dead clicks, frantic scrolling or an immediate bounce. This needs analytics to be on for your project. | Then set how often: - **Show each person only once**: on, each person sees it once. - **Days before showing again**: how long before it can show again. 0 means it can come back on the next visit. - **Max times per person**: 0 means no limit. - **Starts** and **Ends**: the dates it runs between. Leave them as **Any time** to show it whenever it's switched on. It runs through the end of the **Ends** day. ## How visitors see popups - Only one popup shows per visit. When several match, the first one in your list wins, so drag them into the order you want. - It doesn't show while the widget is open, while a survey or the **What's new** card is showing, or when the launcher is hidden. - Hovering over the message pauses its timer. Visitors close it with the small cross. ## Turn a message off, change it or delete it On **Popups**, use the switch next to a message to turn it off or on, or select **Edit** to change it. To remove one, open it and select **Delete**. Select **Save** after any change. ## See how it's doing Under each message, the list shows how many times it was **Shown**, and the share of those views that were **Opened** or **Closed**. The numbers cover the last 30 days. Opened means the visitor selected the message or a quick reply. You can also start a popup from **Customers**, **Messaging**: select **New campaign**, then **In-app popup**. ## Check it worked Open a page that matches your settings in a private browser window and wait for the trigger. The message appears beside the launcher. Popups show once per visit, so open a new private window to see it again. ## Troubleshooting ### The popup doesn't show on my site - Check that the message's switch is on and that today is between its **Starts** and **Ends** dates. - Check **Hide the launcher** is off under **Look**. Popups need the launcher. - Check the page address matches **Only on these pages**, and isn't in **Never on these pages**. - You may have seen a popup already in this visit. Try a new private window. ### I can't pick Team member **Support** is set to Quanta only, so team members can't send popups. Change who answers on the **Support** tab, or send it from Quanta. ### Saving asks me to pick the team member who sends the message The message is from **Team member** but nobody is picked. Pick someone under **Team member**. If the list is empty, add agents on the **Support** tab first. ### It says "A popup message is sent by someone who is not a Support agent" The person you picked was removed from your Support agents. Pick someone else, or add them back on the **Support** tab. ### It says "The end date must be after the start date" Move the **Ends** date after the **Starts** date. ## Read next - [What your users see in the widget](/rectify/help/a/18-what-your-users-see-in-the-widget) - [Sign in verified users](/rectify/help/a/23-sign-in-verified-users) --- # Sign in verified users Collection: Widget URL: https://app.rectify.so/rectify/help/a/23-sign-in-verified-users Tell the widget who is signed in to your site, and sign them in to the Roadmap, Changelog and Help tabs with a signature from your server. > **Note:** **Before you start.** Anyone on your team can add the user details to your script. Only Owners and Admins can see the secret. Members can turn on **Sign verified visitors in** under **Publish**, **Portal**, **Access**, but not on the **Install** page. You need to change code on your server and on your site. There are two levels. Telling the widget who is signed in greets them by name, fills in their name and email in the forms and in Support, and adds them to your contacts. Signing them in as verified also lets them vote, post and comment as themselves in the Roadmap, Changelog and Help tabs. ## Tell the widget who is signed in 1. In your project, open **Publish**, then **Widget**, and select **Install**. 2. Under **Identify visitors**, copy the code from **From your code**. 3. Add it to the object at the end of your Rectify script, and fill in the signed-in user's details from your own app. ```javascript userInfo: { id: 'user_123', email: 'jane@acme.com', name: 'Jane Doe', }, ``` You can write `userId` instead of `id`. Only add `userInfo` when someone is signed in. If you use one of the framework versions of the script, pass `userInfo` as the second value to `RectifyInstance.init`, after your project ID. ![Identify visitors and Who is browsing, under Install.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106104943-01-identify.png) ## Sign them in as verified users Anyone can type an email into a web page, so the Roadmap, Changelog and Help tabs only trust a user your server has signed. 1. On the **Install** page, under **Who is browsing**, turn on **Sign verified visitors in**. It saves straight away, and **How it works** appears under it. ![1 Sign verified visitors in, shown here under Publish, Portal, Access. How it works holds your secret, hidden here.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106106582-02-steps.png) 2. Copy the line under step 1 of **How it works**. It holds your project's secret. 3. On your server, use that line to sign the signed-in user's id. If you don't pass a user id, sign their email in lowercase instead. 4. Add the result as `userHash` to the `userInfo` in your Rectify script. 5. Publish your site. The line you copy in step 2 looks like this, with your own secret in it: ```javascript const userHash = crypto.createHmac("sha256", "YOUR_SECRET").update(userId).digest("hex"); ``` And the `userInfo` in your script looks like this: ```javascript userInfo: { userId: "u_123", email: "jane@acme.com", name: "Jane", userHash } ``` The same switch and steps are under **Publish**, **Portal**, **Access**, in **Signed-in visitors**. There, select **Save** after you turn it on. > **Warning:** Keep the secret on your server. Never put it in your site's code or in the page, or anyone could sign in as anyone. Any server language works. The signature is an HMAC-SHA256 of the user id, or of the lowercase email, with the secret as the key, written as 64 hexadecimal characters. ## What changes for your visitors With **Sign verified visitors in** on: - Visitors with a valid signature vote, post and comment as themselves in the Roadmap, Changelog and Help tabs. - In the Changelog tab they can subscribe to new releases by email. - If your portal is private, signed-in visitors you allow in can open those tabs in the widget. - Visitors without a valid signature stay anonymous in those tabs, so nobody can pose as someone else. With it off, `userInfo` still fills in the forms and adds visitors to your contacts, but they stay anonymous in the Roadmap, Changelog and Help tabs. ## Get a new secret If your secret gets out, select **Regenerate secret** under **How it works**, then **Regenerate**. Your site stops signing visitors in until your server uses the new secret, so update it straight away. ## Check it worked Sign in to your own site, open the widget and select the **Changelog** tab. If you're signed in as a verified user and you passed an email, you see **Get new releases by email** with a **Subscribe** button. ## Troubleshooting ### Visitors still show as anonymous in the Roadmap tab - Check that your server signs exactly the user id you pass in `userInfo`. Sign the lowercase email only when you don't pass a user id. - If you selected **Regenerate secret**, update your server with the new secret. - If your project has a website address, signing in only works on that domain and its subdomains. - Pass `userInfo` in the script itself. A user set later with `RectifyInstance.identify()` isn't signed in to these tabs. ### The Sign verified visitors in switch is greyed out On the **Install** page, only Owners and Admins can change it. Members can turn it on under **Publish**, **Portal**, **Access**, in **Signed-in visitors**, then select **Save**. Only Owners and Admins see the secret, so ask one of them to share the setup with you. ### I don't see How it works The steps show only when **Sign verified visitors in** is on, and only to Owners and Admins. ## Read next - [Install the Rectify widget on your site](/rectify/help/a/5-install-the-rectify-widget) - [What your users see in the widget](/rectify/help/a/18-what-your-users-see-in-the-widget) - [Roles and project access: Owner, Admin and Member](/rectify/help/a/9-roles-and-project-access) --- # The widget doesn't show: what to check Collection: Widget URL: https://app.rectify.so/rectify/help/a/24-the-widget-does-not-show Five checks that find why the Rectify widget isn't appearing on your site. Work through these checks in order. Most problems are solved by the first two. ## 1. Check the widget is switched on Open **Publish**, then **Widget**, and select **Install**. **Widget on your site** must show **Live**. When it shows **Paused**, the widget is hidden on every page, even though your script is still there. ![1 Widget on your site, under Status. Live means it shows on your site.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106109340-01-status.png) ## 2. Check the script is on the page Open your site, open your browser's developer tools and search the **Elements** panel for `widget.umd.js`. If it isn't there, the script was never added, or your site builder hasn't published it yet. Add it again with [Install the Rectify widget on your site](/rectify/help/a/5-install-the-rectify-widget). ## 3. Check the project ID Find the line that starts with `projectId` in the script on your site. It must match the one in the script under **Install**. If they differ, copy the script from **Install** again and replace the old one. If your browser console shows **Project ID is required to initialize the widget**, the `projectId` line is missing from your script. ## 4. Check the launcher isn't hidden Select **Look** on the Widget page and make sure **Hide the launcher** is off. Also check that your script doesn't set `hideLauncher: true`, because the setting in your code wins. With the launcher hidden, the widget only opens from your own button through `RectifyInstance.control('open')`. ![4 Hide the launcher, under Look.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106110952-02-hide-launcher.png) A site, or some pages on it, can also hide the launcher with settings of their own. Under **Sites**, each site's line sums up what it changes. Open the site, and any page settings under **Pages**, and check that **Launcher** is set to **Show**. See [Give a site or page its own launcher](/rectify/help/a/127-give-a-site-or-page-its-own-launcher). ## 5. Check nothing blocks the widget Open your browser's developer tools, select **Network** and reload the page. Look for `widget.umd.js` and for a request to `api.rectify.so` that ends in `/widget`. If either is blocked or fails: - An ad blocker or privacy extension may be stopping it. Try a private window with extensions off. - Your site's Content Security Policy may not allow Rectify. Add `https://api.rectify.so` to the scripts and connections it allows. > **Note:** The widget shows nothing at all when it can't load its settings, for example with a wrong project ID or a blocked request. Checks 3 and 5 find both. --- # How requests, boards and the roadmap fit together Collection: Roadmap and changelog URL: https://app.rectify.so/rectify/help/a/53-how-requests-boards-and-the-roadmap-fit-together What posts, boards, statuses and roadmaps are, how they connect, and where each one lives in Rectify and on your portal. > **Note:** **Before you start.** The roadmap is on every plan. Owners, Admins and Members can add and edit posts, boards, statuses, tags and roadmaps. Only Owners and Admins can delete them, merge posts, change many posts at once, and approve or decline posts that wait for review. Your customers tell you what they want, vote on each other's ideas and follow along as you build. Four pieces hold this together: posts, boards, statuses and roadmaps. ![1 Boards. 2 A status column. 3 A post.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106326123-01-roadmap.png) ## Posts A post is one request or idea, such as "Dark mode". It has a title, a description, votes, comments and followers. Your team can also give it tags, a target date, an assignee and a checklist. Posts come from three places: - **Your portal.** Visitors post on the **Requests** page, or select **Suggest an idea** on the **Roadmap** page. - **Your widget.** The **Roadmap** tab has a **Requests** list with a **New request** button. - **Your team.** Select **Add post** in Rectify, for yourself or on a customer's behalf. Posts from your portal and widget can wait in the **Review queue** before anyone else sees them. Posts your team adds go live straight away. ## Boards A board is where posts live. Every post sits on exactly one board, and you can move it to another one. Each board decides who can see it, vote, comment and post on it, and whether new posts wait for review. A new project comes with one board, **Feature Requests**. Add more to keep different kinds of requests apart, for example one for integrations or one for your mobile app. On your portal, visitors can pick a board on the **Requests** and **Roadmap** pages. ## Statuses A status says where a post is in your plan. Statuses are shared by every board and every roadmap. Each one belongs to a group: | **Group** | **Means** | **Starts with** | | --- | --- | --- | | **Reviewing** | Not committed yet | **Backlog**, where new posts land | | **Planned** | Committed and queued | **Planned** | | **Active** | Being built. Posts here can have a stage, such as **In beta** | **In Progress** | | **Completed** | Live. Changelog posts link requests from here | **Shipped** | | **Canceled** | Won't do | **Closed** | Changing a post's status never emails anyone by itself. After each move, Rectify asks whether to tell its followers. ## Roadmaps A roadmap is a view of your posts. It doesn't hold posts of its own: it shows the posts that match it, so the same post can appear on several roadmaps at once. Deleting a roadmap leaves every post, vote and comment where it was. Each roadmap has one of two layouts: - **Status columns:** one column per status. Dragging a card to another column changes its status everywhere, including on your portal. - **Timeline:** one column per month, quarter or half year, based on each post's target date. Dragging a card changes its target month. A new project comes with one roadmap, **Roadmap**, with **Planned**, **In Progress** and **Shipped** columns. Each roadmap can be **Public**, **Internal** (only your team sees it) or limited to **Segments** of your contacts, and it can show only some boards, statuses, tags or authors. ## Where you work In the sidebar, open **Roadmap**: - **Roadmaps** lists your roadmaps. Open one to work on its board. - **All posts** is a table of every post, with filters and changes to many posts at once. - **Review queue** holds posts and comments waiting for approval. The number next to it is how many are waiting. - **Changelog** is where you announce what shipped. ![The Roadmap section of the sidebar and the Roadmaps page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106327878-02-roadmaps.png) ## Read next - [Set up boards and statuses](/rectify/help/a/54-set-up-boards-and-statuses) - [Manage posts and votes](/rectify/help/a/55-manage-posts-and-votes) - [Share your public roadmap](/rectify/help/a/58-share-your-public-roadmap) - [Write and publish a changelog post](/rectify/help/a/59-write-and-publish-a-changelog-post) --- # Set up boards and statuses Collection: Roadmap and changelog URL: https://app.rectify.so/rectify/help/a/54-set-up-boards-and-statuses Add boards with their own access and review rules, and shape the statuses your posts move through. > **Note:** **Before you start.** Boards and statuses are on every plan. Owners, Admins and Members can add and change boards, statuses and tags. Only Owners and Admins can delete them. Boards and statuses are shared by every roadmap and by your portal. Changes apply straight away, so there's nothing to save. ## Add a board 1. In the sidebar, open **Roadmap**, then **Roadmaps**, and select **Boards & statuses**. ![1 Boards & statuses, at the top of the Roadmaps page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106330988-01-open.png) 2. On the **Boards** tab, select **New board**. ![2 New board.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106332829-02-boards.png) 3. Enter a name, and a description if you like. To give the board an icon, select the smiley next to the name. The icon shows on the roadmap tabs and cards. 4. Under **Who can do what**, choose who can **View**, **Vote**, **Comment** and **Submit** on this board. ![3 The board's name. 4 Who can do what.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106334481-03-new-board.png) 5. Under **Moderation**, choose whether new posts and comments on this board wait for review. 6. Under **Submit form**, select **Add field** to ask extra questions when someone posts. 7. Select **Create board**. ![5 Moderation. 6 Add field. 7 Create board.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106336116-04-moderation.png) You can also add a board from a roadmap: select **+** at the end of the board tabs. ## Who can do what Each action has its own setting: | **Setting** | **Who it lets in** | | --- | --- | | **Anyone** | Everyone who opens your portal. Visitors without an account confirm their email the first time they act. | | **Signed in** | People with a portal account. | | **Segments** | Only contacts in the segments you pick. | | **Team only** | Your team. Everyone else can't see the board at all. | Nothing can be more open than **View**. For example, if only signed-in people can view a board, you can't let anyone vote on it. ## Review rules for a board **Moderation** has three settings: **Posts from visitors** (people who haven't signed in), **Posts from signed-in users** and **Comments**. Each one can be: - **Use portal default:** follow the rule set for the whole portal. - **Always review:** hold everything for review. - **Never review:** publish straight away. Your portal holds posts with images or external links for review whatever the board says, as long as those holds are switched on. [Moderate new posts in the review queue](/rectify/help/a/56-moderate-new-posts-in-the-review-queue) explains the portal rules. ## Extra questions on the submit form The title and description are always asked. Each extra question has a type: **Short text**, **Number**, **Choice**, **Date** or **Yes / no**. For **Choice**, enter the options separated by commas. Switch on **Required** to make people answer it. Switch off **Show the answer publicly** to keep the answer for your team. A board can have up to 20 questions. ## Change or delete a board On the **Boards** tab, open the menu on a board: - **Edit board** opens the same settings. Select **Save changes** when you're done. - **Delete board** removes it from your portal and the submit form, and can't be undone. Its posts move to the deleted posts and are removed for good after 30 days. To restore one, you pick another board for it. Select the icon next to a board to change it. You can't delete your only board. ## Add a status 1. In **Boards & statuses**, open the **Statuses** tab. 2. Under the group that fits, select **Add status**. 3. Type a name and select **Add**. ![The Statuses tab, and 2 Add status under Active.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106337587-05-statuses.png) The groups are **Reviewing**, **Planned**, **Active**, **Completed** and **Canceled**. The group decides what a status means elsewhere in Rectify. Posts in an **Active** status can have a stage: **Building**, **In beta**, **Fix in review** or **Rolling out**. Posts in a **Completed** status can be linked to changelog posts. ## Change a status On each status: - Select its name to rename it. Names can be up to 80 characters. - Select the coloured square to change its colour, and the icon next to it to change its icon. - Drag the handle to reorder statuses within a group. - **Roadmap**: switch on to give new roadmaps a column for this status. Roadmaps you already have don't change. The menu (**⋮**) has **Rename**, **Make default**, **Move to** another group, and **Delete**. The default status is where new posts land. Moving a status out of **Active** clears the stage on its posts. ![The Roadmap switch and the menu on a status.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106339057-06-status-menu.png) ## Delete a status You can only delete a status that no post uses and that isn't the default. Move its posts to another status first. Roadmap columns that use the status lose that column. ## Check it worked Open a roadmap. New boards show as tabs above the columns, and new statuses show in every **Status** menu. On your portal, a board appears for everyone allowed to view it. ### "Delete" is missing from the menu Only Owners and Admins can delete boards, statuses and tags. Ask one of them. ### It says "Make another status the default first" The default status can't be deleted. Open the menu on another status, select **Make default**, then delete the first one. ### It says "Move the posts on this status first" Posts still use the status, including posts waiting for review or merged into others. Move them to another status, then try again. ### It says "cannot be more open than View" One of **Vote**, **Comment** or **Submit** lets in more people than **View**. Loosen **View**, or tighten the others. ### It says "Keep at least one board so posts have a home" Every project needs a board. Add another board before you delete this one. ## Read next - [Manage posts and votes](/rectify/help/a/55-manage-posts-and-votes) - [Moderate new posts in the review queue](/rectify/help/a/56-moderate-new-posts-in-the-review-queue) --- # Manage posts and votes Collection: Roadmap and changelog URL: https://app.rectify.so/rectify/help/a/55-manage-posts-and-votes Add posts for your customers, keep their status and details up to date, add or remove votes, and tidy up many posts at once. > **Note:** **Before you start.** Owners, Admins and Members can add and edit posts, change their status, reply, and add or remove votes. Only Owners and Admins can delete and restore posts, change many posts at once, merge posts, and remove comments. ## Add a post Use this to log a request you heard on a call, in an email or in a chat. 1. Open a roadmap, or **All posts**, and select **Add post** at the top. To add a post straight into a column, select **+** next to the column's name instead. 2. Enter a title. 3. Add more detail below it. Type `/` to add other blocks, and `@` to mention a teammate. 4. Pick the board and the status. New posts start on your default status. 5. If you like, add **Tags**, an **Assignee** and a **Target** date. 6. To log it for a customer, select **You**, search for them under **Who is asking?** and pick them. They become the author, get the first vote and follow the post, so they hear about updates instead of you. 7. Select **Add post**. ![2 Title. 4 Board and status. 6 Who is asking. 7 Add post.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106341520-01-add-post.png) While you type the title, Rectify lists posts that already look similar. Select one to open it and add a vote there instead of posting twice. Switch on **Keep open** to add several posts in a row. Posts your team adds go live straight away, without review. The customer isn't emailed when you log a post for them. ## Change a post's details 1. Select a card on a roadmap, or a row in **All posts**, to open the post. 2. In the right-hand panel, change its **Status**, **Stage**, **Board**, **Tags**, **Target** or **Assignee**. Each change saves straight away. ![2 Status, Stage, Board, Tags, Target and Assignee.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106343173-02-details.png) **Stage** shows only while the post is in an **Active** status, such as **In Progress**. The target date shows as a month on your roadmap. Moving a post to another board means that board's rules decide who can see it and vote on it. When you change the status, Rectify asks whether to send an update to the post's followers. Nothing is sent unless you choose to. [Notify followers when you ship](/rectify/help/a/60-notify-followers-when-you-ship) explains the update and who gets it. On a roadmap with status columns, you can also drag a card to another column. To change the title or description, select **More** (**…**) at the top of the post, then **Edit post**, and select **Save changes** when you're done. ## Pin, lock or share a post The icons at the top of an open post: - **Pin to the top of the board** puts the post first under **Most votes**, on your roadmaps and on your portal. - **Lock the thread** stops customers from commenting. Your team can still reply. - **Copy link** copies a link that opens this post in Rectify. ## Add or remove a vote Add a vote for a customer who asked for something by email, chat or call. 1. Open the post and select **Manage** next to the votes. 2. Search for the customer by name or email. 3. Select them under **Add a vote**. ![2 Search. 3 The customer to add.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106345016-03-votes.png) If they aren't a contact yet, type their name, select **Create "…" as a new contact**, enter their **Name** and **Email**, and select **Create & add vote**. To take a vote back, point at a voter and select **Remove vote**. The arrow button next to the vote count adds or removes your own vote. People you add a vote for follow the post. Nobody is emailed when you add or remove a vote. The menu next to each voter sets what they hear about this post: **All activity**, **Status changes** or **Unsubscribe**. Voters without an email address show **No email**. ## Reply to a post Write in the comment box under the post and select **Comment**. Before you send: - **Public** or **Team only:** public comments show on your portal and email followers who chose **All activity**. Team-only comments stay inside Rectify and notify nobody. - **Change status:** pick a status to change it with your comment. The button becomes, for example, **Comment & mark In Progress**. ## Delete or restore a post 1. Open the post, select **More** (**…**), then **Delete post**. 2. Select **Delete** to confirm. The post leaves your portal straight away. For 30 days you can bring it back: in **All posts**, select **Filter**, then **Deleted only**, open the post and select **Restore**. After 30 days it's removed for good, with its uploads. ## Change many posts at once In **All posts**, tick the posts you want to change. A bar appears at the bottom with **Status**, **Board**, **Tag**, **Assign** and **Delete**, plus **Merge** when exactly two posts are ticked. Rectify asks you to confirm each change, and there's no bulk undo. ![The bar that appears when posts are ticked.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106346483-04-bulk.png) ## Check it worked The post shows its new details on every roadmap it matches and, for public boards, on your portal. Open the **Activity** tab under the post to see each change and who made it. ### I can't find Delete post or the bar for many posts Only Owners and Admins can delete posts and change many posts at once. Ask one of them. ### The customer I'm looking for isn't listed The search lists contacts that have an email address. Type their full name, select **Create "…" as a new contact**, and add their email. ### Stage is missing The post isn't in an **Active** status. Move it to one, such as **In Progress**, and **Stage** appears. ## Read next - [Merge duplicate requests](/rectify/help/a/57-merge-duplicate-requests) - [Notify followers when you ship](/rectify/help/a/60-notify-followers-when-you-ship) - [Set up boards and statuses](/rectify/help/a/54-set-up-boards-and-statuses) --- # Moderate new posts in the review queue Collection: Roadmap and changelog URL: https://app.rectify.so/rectify/help/a/56-moderate-new-posts-in-the-review-queue Choose which posts and comments wait for review, then publish, decline or merge them from the review queue. > **Note:** **Before you start.** The review queue is on every plan. Owners and Admins can publish, approve and decline. Members can read the queue but can't act on it. Owners, Admins and Members can change the portal's review rules. New posts and comments from your portal and from your widget's **Roadmap** tab can wait in the review queue before anyone else sees them. Nothing in the queue is public until you approve it. Posts your team adds in Rectify never wait. ## What waits for review Out of the box, these wait: - Posts and comments from people who haven't signed in to your portal. - Anything with an image. - Anything with an external link. Everything else appears straight away. You can change these rules for the whole portal, and override them on each board. ## Publish or decline a post 1. In the sidebar, open **Roadmap**, then **Review queue**. The number next to it is how many items are waiting. 2. Read the post. Next to **Publish to**, pick the status it should start in. It starts on your **Planned** status. 3. Select **Publish**, or **Decline** to keep it off your portal. ![2 Publish to. 3 Publish, with Decline and Merge instead next to it.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106348958-01-queue.png) When you publish, the post appears on your portal and roadmaps, and Rectify tells its author it's live by email and in their portal notifications. When you decline, the post stays hidden and its author hears it wasn't approved. A declined post can't be published later. Use **Everything**, **Posts** and **Comments** at the top to switch between kinds, **Board** to show some boards only, and **Search the queue** to find something. ## Ideas from Discord If your project is connected to Discord, ideas sent from your server wait here too. With **Review before they go public** on, which is the default, every Discord idea waits, whatever your review rules say. Turn it off under **Integrations**, **Discord**, and Discord ideas follow your rules instead, with people from Discord counted as signed in. When you publish or decline an idea from someone who asked for updates, they get a Discord DM instead of an email. [Collect ideas and bug reports from Discord](/rectify/help/a/133-collect-ideas-and-bug-reports-from-discord) explains how ideas arrive. ## Approve or decline a comment Comments show the post they're on. Select **Approve** to publish the comment, or **Decline** to keep it hidden. An approved comment reaches the post's followers like any other comment. When you decline, its author hears it wasn't approved. ## Merge instead of publishing If a new post looks like one that's already published, the queue shows how close the match is, the matching post and its votes. Select **Merge instead** to fold the new post into the existing one. Its author's vote moves across, and the new post never appears on its own. [Merge duplicate requests](/rectify/help/a/57-merge-duplicate-requests) explains merging. ## Review from the post itself A post waiting for review also shows in **All posts**, marked **In review**. Open it to see **Waiting for review. Nothing is public until you approve it.** at the top, and select **Approve** or **Decline** there. ## Choose what waits for review 1. In the sidebar, open **Publish**, then **Portal**. 2. On the **Requests** tab, which opens first, scroll to **Review**. 3. Under **What waits for review**, pick **Nothing waits**, **Visitors only**, **Signed-in only** or **Everything waits**. 4. Turn **Hold anything with an image** and **Hold anything with an external link** on or off. ![3 What waits for review. 4 Hold anything with an image, with the link hold below it.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106350601-02-rules.png) 5. Select **Save**. These rules cover posts and comments. The image and link holds apply even on boards set to **Never review**. To set different rules for one board, open **Roadmap**, **Roadmaps**, **Boards & statuses**, then **Edit board** on that board, and use **Moderation**. [Set up boards and statuses](/rectify/help/a/54-set-up-boards-and-statuses) shows how. ## What the person who posted sees On your portal, they're told their post waits for the team to review it. In the widget they see "Thanks. The team will review your request before it appears." They can still open their own post while it waits. Nobody else can. ## Check it worked The item leaves the queue and the count in the sidebar goes down. Published posts show on your portal for everyone allowed to view their board. ### Publish and Decline are missing Only Owners and Admins can act on the queue. Members see a note saying so. Ask an Owner or Admin. ### A post I expected isn't in the queue It may not have needed review. Posts your team adds never wait, and with **Nothing waits**, only posts with images or links, or on boards set to **Always review**, are held. Look for it in **All posts**. ### I want to publish a post I declined Declined posts can't go back to the queue. Add the request again with **Add post**, on the customer's behalf if you like. ## Read next - [Merge duplicate requests](/rectify/help/a/57-merge-duplicate-requests) - [Set up boards and statuses](/rectify/help/a/54-set-up-boards-and-statuses) - [Control who can see the portal](/rectify/help/a/43-control-who-can-see-the-portal) --- # Merge duplicate requests Collection: Roadmap and changelog URL: https://app.rectify.so/rectify/help/a/57-merge-duplicate-requests Combine two posts that ask for the same thing, so their votes and followers count once, and undo a merge if you need to. > **Note:** **Before you start.** Only Owners and Admins can merge and unmerge posts. Members can see suggested duplicates and mark them as not a duplicate. Merging is on every plan. When two posts ask for the same thing, merging folds one into the other. The post you keep gets the votes and followers of both, and the merged post's comments show on it. ## How Rectify spots duplicates Each time a post is added, Rectify compares its wording with your other posts and flags close matches. Flagged posts show a count at the top of your roadmap, such as **2 possible duplicates**, and a banner at the top of **All posts** with a **Review** button. Select either one to show only the flagged posts. While someone types a new post, on your portal or in Rectify, they also see similar posts that already exist, so they can vote there instead. ## Review a suggested duplicate 1. Open a flagged post. The banner at the top shows the matching post, how close the match is and its votes. 2. Choose what to do: - **Merge in** merges the matching post into the one you have open. - **Not a duplicate** hides the suggestion. The same pair isn't suggested again. ![Merge in and Not a duplicate, in the banner of a flagged post.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106353611-01-suggestion.png) To keep the other post instead, use the steps below and select **Swap**. ## Merge two posts 1. Open the post you want to fold into another one. 2. Select the merge icon (**Merge**) at the top of the post. 3. Search for the post to keep, and select it. With no search, the closest matches come first. 4. Check the line at the bottom: the crossed-out post is merged into the other one. Select **Swap** to merge the other way round. 5. Select **Merge posts**. ![3 The post to keep. 4 Which post is merged into which, and Swap. 5 Merge posts.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106355243-02-merge-dialog.png) You can also tick exactly two posts in **All posts** and select **Merge** in the bar at the bottom. It opens the same window. In the **Review queue**, a new post that matches an existing one has **Merge instead**. ## What a merge does - Votes and followers are copied to the post you keep. Someone who voted for both posts counts once. - Comments from the merged post show on the post you keep, marked with the post they came from. - The merged post leaves your roadmaps, your lists and your portal. Its old link on the portal says it was merged and links to the post you keep. - Status, tags and board stay as they were on both posts. - Nobody is emailed. Followers of the merged post hear about future updates you send from the post you keep. The count under **Survivor keeps** adds up both posts. The real count after the merge can be lower, because people who voted for both count once. ## Undo a merge 1. Open the merged post. It shows **Merged into** and the name of the post you kept. 2. Select **More** (**…**), then **Unmerge**. ![The Merged into banner, and 2 Unmerge.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106356901-03-merged.png) The post comes back with its own votes, followers and comments, and they're taken off the post you kept. Merged posts don't appear in lists, so open one from a link to it. If you merged the post you had open, it stays open after the merge, so you can undo straight away. ## Change how duplicates are found 1. In the sidebar, open **Publish**, then **Portal**. 2. On the **Requests** tab, which opens first, scroll to **Duplicates**. 3. Turn **Detect duplicates** on or off, and move **Match sensitivity** to change how close two posts must be before one is flagged. 4. Select **Save**. Matching looks at wording. To have AI double-check each match, turn on **AI check** at the top of the **Review queue**. It's available when your organization can use AI, through your plan's AI credits or your own provider under **Organization settings**, **AI providers**. ### I can't find the merge icon Only Owners and Admins can merge posts. Ask one of them, or select **Not a duplicate** if the posts are different. ### It says "Post is already merged" That post was merged before. Open the post it was merged into and merge into that one instead, or unmerge it first. ### It says "Cannot merge into a merged post" The post you picked to keep was itself merged into another one. Pick the post it was merged into. ## Read next - [Manage posts and votes](/rectify/help/a/55-manage-posts-and-votes) - [Moderate new posts in the review queue](/rectify/help/a/56-moderate-new-posts-in-the-review-queue) --- # Share your public roadmap Collection: Roadmap and changelog URL: https://app.rectify.so/rectify/help/a/58-share-your-public-roadmap Choose which roadmaps your customers see on your portal and in your widget, pick the one that opens first, and copy a link to share. > **Note:** **Before you start.** Public roadmaps are on every plan. Owners, Admins and Members can change a roadmap's settings, make it the default and copy its link. Only Owners and Admins can delete a roadmap. Every project's portal has a **Roadmap** page at `app.rectify.so/` followed by your portal address and `/roadmap`. It's in the portal menu from the start, and the same roadmaps show in your widget's **Roadmap** tab. ## Choose who can see a roadmap 1. In the sidebar, open **Roadmap**, then **Roadmaps**, and open the roadmap. 2. Select **This roadmap**, the sliders icon at the top of the page. 3. Under **Who can see it**, pick who it's for: - **Public:** anyone who can open your portal. - **Internal:** only your team. It never shows on the portal or in the widget. - **Segments:** only contacts in the segments you pick. Pick at least one. 4. Under **Which posts appear**, narrow it down by **Boards**, **Statuses**, **Tags** or **Author segments** if you like. A post has to match everything you set here. Leave a filter empty to allow all. 5. Select **Save**. ![3 Who can see it. 4 Which posts appear. 5 Save.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106359704-02-who-can-see.png) Some posts never show on a public roadmap, whatever you pick: posts on boards that visitors can't view, posts waiting for review or declined, merged posts and deleted posts. ## Copy the link 1. In the sidebar, open **Roadmap**, then **Roadmaps**. 2. Select **Copy link** next to the roadmap. Rectify says **Public link copied**, or **Portal link copied** for a roadmap shown to segments. ![2 Copy link, next to a public roadmap.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106361144-01-copy-link.png) The link opens your portal on that roadmap, for example `app.rectify.so/acme-app/roadmap?roadmap=integrations`. If your organization has its own domain set up, the link uses it. Internal roadmaps have no link to copy. To look at a roadmap as visitors do, open it in Rectify and select **Open in portal**, the arrow icon at the top. ## Pick the roadmap that opens first Your default roadmap, marked **Default**, opens first on your portal and in your widget. To change it, open the menu (**⋮**) next to another roadmap on the **Roadmaps** page and select **Make default**. When you have more than one public roadmap, visitors can switch between them: the roadmap's name at the top of the portal page becomes a menu, and the widget shows a picker. ## Show a different set of posts You can have several roadmaps, each showing different posts. For example, one for your whole product and one for integrations only. 1. On the **Roadmaps** page, select **New roadmap**. 2. Pick a **Layout**: **Status columns**, with one column per status, or **Timeline**, with one column per month, quarter or half year based on each post's target date. A timeline shows the current period, the next three and a **No date** column. 3. Enter a **Name** of up to 50 characters, and a description if you like. Visitors see the description under the name. 4. For status columns, check the **Columns**. Select **Add column** to add one, select a name to relabel it, and drag to reorder. For a timeline, pick the **Periods**. 5. Set **Who can see it** and **Which posts appear**. 6. Select **Create**. Posts aren't copied: each roadmap shows the posts that match it, so changes to a post show everywhere at once. ## What visitors see On your portal, visitors see your columns with a card for each post. They can vote right on a card, open it to read and comment, switch boards with the tabs at the top, filter, search and sort by **Top**, **New** or **Discussed**. **Suggest an idea** lets them post a request on any board they're allowed to post on. ![The public Roadmap page, with the roadmap menu at the top.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106362959-03-portal.png) In your widget, the **Roadmap** tab shows the roadmap under **Roadmap**, with a button for each column, and visitors' ideas under **Requests**. [Choose the widget's tabs](/rectify/help/a/20-choose-the-widgets-tabs) shows how to turn the tab on. ## Check it worked Open the link in a private browser window, where you're not signed in. You should see the roadmap as a visitor does. Roadmaps limited to segments only show for contacts in those segments. ### Copy link is missing The roadmap is **Internal**. Change **Who can see it** to **Public** or **Segments** first. ### A post is missing from the public roadmap Check that its status is one of the roadmap's columns and that it matches **Which posts appear**. On a timeline, posts dated before the current period, or more than three periods ahead, don't show. Posts on boards visitors can't view, and posts waiting for review, don't show either. ### Visitors are asked to sign in Your whole portal is private, or only open to some people. [Control who can see the portal](/rectify/help/a/43-control-who-can-see-the-portal) explains the portal's access settings. ### The roadmap isn't in the portal menu Someone turned **Roadmap** off under **Pages in the menu**. That only hides it from the menu: the page and its link still work. [Set up your public portal](/rectify/help/a/41-set-up-your-public-portal) shows how to turn it back on. ## Read next - [How requests, boards and the roadmap fit together](/rectify/help/a/53-how-requests-boards-and-the-roadmap-fit-together) - [Notify followers when you ship](/rectify/help/a/60-notify-followers-when-you-ship) - [Control who can see the portal](/rectify/help/a/43-control-who-can-see-the-portal) --- # Write and publish a changelog post Collection: Roadmap and changelog URL: https://app.rectify.so/rectify/help/a/59-write-and-publish-a-changelog-post Write an update with a cover and labels, then publish it now or schedule it for your portal, widget and RSS feed. > **Note:** **Before you start.** Owners, Admins and Members can write, edit, schedule and publish posts. Only Owners and Admins can create labels, resend a post's email, or delete a post. The changelog is on every plan. ## Write the post 1. In the sidebar, open **Roadmap**, then **Changelog**. 2. Select **New update**. ![2 New update, at the top of the Changelog page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106365718-01-new-update.png) 3. Type a title where it says **What shipped?**. 4. Write the update below the title. Type `/` to add headings, lists, images, code, tables and more. 5. To add a cover image, select **Add cover** above the title. You can upload an image, generate one with Quanta, or pick a colour. 6. To add labels, select the label icon at the top of the right-hand rail and tick the labels that fit. ![3 Title. 4 The update. 5 Cover. 6 Labels, in the right-hand rail.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106367638-02-editor.png) Rectify saves as you type. The top bar shows **Saving**, then **Saved**, next to the post's status: **Draft**, **Scheduled** or **Published**. Nothing is saved until the post has a title. > **Tip:** Linked a few shipped requests already? **Draft with Quanta**, at the bottom of the rail, writes the title and body from them, or from a few lines you give it. It replaces what you've written so far. ## Add a cover image Covers are 16:9 and show above the post on your portal and when someone shares its link. Select **Add cover**, then: - **Upload an image:** pick a PNG or JPG. Drag to position it, use **Zoom** if you need to, then select **Use cover**. Rectify saves it at up to 1600 pixels wide, and the cropped file must be under 5 MB. For a sharp result, start from an image of 1600 x 900 pixels or more. - **Generate with Quanta:** paints a cover from your title and body. This needs a Gemini API key, which you add under **Organization settings**, **AI providers**. - **Or a color:** a plain colour band instead of an image. Hover over a cover to replace it, regenerate it, view it full size or remove it. ## Add labels Labels such as New, Improved and Fixed tell readers what kind of change it is. On your portal, readers can filter the changelog by label. ![The labels panel, with New label at the bottom.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106369678-03-labels.png) A post can carry up to 10 labels. To make a new one, Owners and Admins select **New label** in the panel, enter a name, pick a colour and select **Add label**. The new label is added to the post straight away. To rename, reorder or delete labels, select **Settings** at the top of the Changelog page and open **Labels**. ## Publish now or schedule it 1. Select **Publish** in the top bar. It stays greyed out until the post has a title and some text. 2. Under **When**, pick **Publish now**, or pick **Schedule** and choose the date and time it goes out. 3. Tick **Email subscribers** to email the update, or untick it to publish quietly. 4. Select **Publish now**, or **Schedule update**. ![2 Publish now. 3 Email subscribers. 4 Publish now.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106371589-04-publish.png) The line above the buttons sums up what will happen, for example "Publishes now and emails 38 subscribers." A post you publish quietly is marked as announced, so it never emails anyone later, and it isn't posted to Discord. If your project has segments, **Notify segments** lets you pick some. Leave it empty to reach everyone. Picking segments does more than narrow the email: only people in those segments can see the post on your portal, in the widget and in the feed. [Notify followers when you ship](/rectify/help/a/60-notify-followers-when-you-ship) explains who gets the email and how to tell the people who asked for the feature. ## Where your post appears - **Your portal:** the **Changelog** page, newest first, at `app.rectify.so/your-portal-address/changelog`. Each post also has its own page. - **Your widget:** the **Changelog** tab, when it's switched on. A dot on the tab tells visitors there's something new. - **RSS:** the feed icon next to **Subscribe** on the portal's Changelog page links to the feed, at `/changelog/feed.xml` after your portal address. It lists your 50 newest posts. - **Discord:** when your project is connected to Discord with a **Changelog channel**, Rectify posts the update there when it goes live. Posts published quietly or limited to segments aren't posted. [Share roadmap and changelog updates in Discord](/rectify/help/a/134-share-roadmap-and-changelog-updates-in-discord) shows what it looks like. ![The portal's Changelog page, with the RSS feed icon.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106373206-05-portal.png) ## Edit, unpublish or delete a post - **Edit:** open the post and change it. On a published post, your changes go live as soon as they're saved, and nobody is emailed again. A copy already posted to Discord is updated to match. - **Change the date readers see:** on a published post, select the calendar icon, **Public date**, in the rail and pick a date. It only changes the date on your changelog and sends no notifications. - **Unpublish:** on the Changelog page, open the post's menu and select **Move back to draft**. It comes off your portal, widget and feed. For a scheduled post, select **Cancel schedule**. - **Duplicate:** select **Duplicate** in the menu to start a new draft from a copy. - **Delete:** Owners and Admins select **Delete** in the menu. The post comes off your portal straight away. It stays under **Deleted** for 30 days, where you can **Restore** it, and is then removed for good. ## Check it worked Open the **Published** tab on the Changelog page to see the post with its date. Then select **View portal** on the **Portal** page under **Publish**, or open `app.rectify.so/your-portal-address/changelog`, and look for it at the top. ### Publish is greyed out Add a title and write something in the body first. Hover over the button to see what's missing. ### It says "Pick an image file" or "Keep covers under 5MB" Covers must be images. If the cropped cover is over 5 MB, save the image as a JPG, or make it smaller, and upload it again. ### My post isn't on the portal Check its status. A **Scheduled** post appears at its scheduled time, and a **Draft** doesn't appear at all. If you picked segments, only people in them can see it. If the changelog is set to signed-in readers, visitors must sign in first. ### Generate with Quanta asks for a Gemini key Cover images are painted with Gemini. Add a Gemini key under **Organization settings**, **AI providers**, or upload your own image instead. ## Read next - [Notify followers when you ship](/rectify/help/a/60-notify-followers-when-you-ship) - [Set up your public portal](/rectify/help/a/41-set-up-your-public-portal) --- # Notify followers when you ship Collection: Roadmap and changelog URL: https://app.rectify.so/rectify/help/a/60-notify-followers-when-you-ship Tell the people who asked for a feature that it's live, when you move their request and when you announce it in the changelog. > **Note:** **Before you start.** Owners, Admins and Members can send updates to followers and publish changelog posts. Emails go to customers who have an email address on file. There are two ways to tell people that what they asked for has shipped. Send an update when you move the request to a shipped status, and link the request to the changelog post that announces it. You can do either or both. ## Who follows a request People follow a request automatically when they post it, vote for it or comment on it. Taking a vote back doesn't unfollow them. People in your Discord server only follow when they choose to, with the DM box in the form or **Follow** on a card. On your portal, each request has a **Follow** button. Followers can choose **All activity**, **Status changes** or **Unsubscribe**. People who pick **Unsubscribe** get nothing about that request. ## Tell followers when you move a request Moving a request never emails anyone on its own. After each move, Rectify asks whether to tell its followers. 1. Open the request from your roadmap or from **All posts**. 2. Change its **Status** to one in the **Completed** group, such as **Shipped**. 3. Rectify shows who will hear about it and a message ready to go. Edit the message if you like. 4. Select **Send to** followers to send it, or **Don't send** to skip it. ![3 The message. 4 Send to 11 followers.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106375772-01-move.png) Followers get the message by email and in their portal notifications. The email's subject is the request's title followed by "is now live". For other statuses, the subject starts with "Update on". The message can be up to 2,000 characters. If your project is connected to Discord, followers who came from your Discord server get the message as a Discord DM instead, and the dialog says how many with "1 of them gets a Discord DM instead." [Share roadmap and changelog updates in Discord](/rectify/help/a/134-share-roadmap-and-changelog-updates-in-discord) shows what they get. If nobody follows the request yet, Rectify says so and there's nothing to send. ## Announce it in a changelog post Link the requests a changelog post ships. When the post goes live, their followers hear about it too. 1. In **Roadmap**, **Changelog**, open the post or select **New update**. 2. Select the link icon, **Shipped posts**, in the right-hand rail. 3. Tick each request this post ships. The list shows requests in the **Completed** group, most votes first. ![2 Shipped posts. 3 A shipped request, ticked.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106377599-02-shipped-posts.png) 4. Select **Publish** in the top bar. 5. Make sure **Email subscribers** is ticked. ![5 Email subscribers, ticked.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106379228-03-email.png) 6. Select **Publish now**, or **Schedule update** for a scheduled post. Within about a minute of the post going live, Rectify emails everyone subscribed to your changelog. Then it emails the followers of each linked request who aren't subscribed, so nobody gets the same post twice. A scheduled post goes out at its scheduled time. On the post's page, the linked requests show under **Shipped in this release**. Followers of linked requests who follow through Discord get a "Shipped" DM at the same time, even while changelog emails are paused. > **Warning:** If you untick **Email subscribers**, nobody hears about the post: not your subscribers, not the followers of linked requests and not your Discord server. The post is marked as announced, so it won't go out later either. ## What people receive The changelog email has your project's name and the post's title as its subject, the start of the post, and a **Read the update** button that opens it on your portal. Every email ends with an **Unsubscribe** link. For a subscriber it stops changelog emails. For a follower it unfollows that one request. People signed in to your portal choose what reaches them on its **Settings** page, under **Notifications**. **Product updates** covers changelog emails, **Shipped** and **Status changes** cover the updates you send when you move a request, and **Pause every email** stops them all. ## Send a post again Owners and Admins can open a published post and select **Resend email**, then **Send again**. Within a minute, everyone subscribed gets it again, including people who already had it, and so do the followers of its linked requests. If your project posts changelog entries to a Discord channel, it's posted there again too. If the post was published quietly, this sends it for the first time. ## Check it worked After you select **Send to** followers, Rectify confirms with "Update sent to" and the number of followers. For a changelog post, select **Subscribers** at the top of the Changelog page to see who is subscribed. ### A request isn't in the Shipped posts list The list only shows requests with a status in the **Completed** group. Move the request to your shipped status first, then open **Shipped posts** again. ### A follower didn't get the email They may have chosen **Unsubscribe** on the request, used an unsubscribe link, or paused emails in their portal settings. They also need an email address on file. If the post was limited to segments, only followers in those segments hear about it. ### It says "Changelog emails are switched off" Changelog emails are turned off for this project. Owners and Admins can turn them back on in **Settings** on the Changelog page, under **Email**. Anyone on your team can also do it under **Publish**, **Portal**: on the **Changelog** tab, turn off **Pause all changelog emails**, then select **Save**. Posts published while emails are off are never emailed afterwards. ## Read next - [Write and publish a changelog post](/rectify/help/a/59-write-and-publish-a-changelog-post) - [Share roadmap and changelog updates in Discord](/rectify/help/a/134-share-roadmap-and-changelog-updates-in-discord) --- # Set up your public portal Collection: Portal and Help Center URL: https://app.rectify.so/rectify/help/a/41-set-up-your-public-portal Name your portal, add your logo, choose the pages in its menu and check its address, then open it for your customers. > **Note:** **Before you start.** Every project gets a portal on every plan, and it's live from the start at `app.rectify.so/` followed by your portal address. Owners, Admins and Members can change and save its settings. Your portal is the public site where customers post requests, vote, follow your roadmap and read your changelog. It can also hold your status page and Help Center. ## Open the portal settings 1. In the sidebar, open **Publish**, then **Portal**. The preview on the left shows your portal as visitors see it, including changes you haven't saved yet. Pick a page to preview above it, and switch between **Desktop** and **Phone**. The **Portal setup** card on the right lists six things to finish: **Logo and name**, **Accent color**, **Pages in the menu**, **Tagline**, **Access rules** and **Custom domain**. Select **Add** next to one to jump to it. The tabs below the card hold the settings: the first is named after the page you're previewing, then **Brand**, **Access** and **Domain and more**. ![The Portal setup card, the settings tabs and View portal.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106229292-01-portal-page.png) ## Name it and add your logo 1. In the sidebar, open **Publish**, then **Portal**. 2. Open the **Brand** tab. 3. Under **Identity**, enter your portal's name. It shows in the header and the browser tab. 4. Add a tagline below it. It's one line under the title on the requests page. 5. Next to **Logo**, select **Upload** to add your logo, or **Replace** to change it. Square works best. 6. Next to **Favicon**, select **Upload** to add the small icon for the browser tab. Use a square image of 32 pixels or more. ![3 Name. 4 Tagline. 5 Logo. 6 Favicon.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106231136-02-identity.png) Names can be up to 120 characters and taglines up to 200. Images must be under 5 MB, and they upload when you save. If your project has its own logo, **Use project logo** puts it back. ## Choose the pages in the menu Further down the **Brand** tab, **Pages in the menu** lists the portal's pages: **Requests**, **Roadmap**, **Changelog**, **Status** and **Help Center**. - Use the switch on a page to show or hide it in the menu. Requests, Roadmap and Changelog start switched on. - Drag a page to change the order. - Open a page with its arrow to give it another name. - Select **Add link** to add a link to your own site, such as your pricing page. Links can open in a new tab. ![Pages in the menu, with Add link.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106232959-03-menu.png) A page you switch off is only hidden from the menu. Anyone with its link can still open it. The **Status** page is the exception: it only opens while it's switched on. ## Check your portal address 1. Open the **Domain and more** tab. 2. Under **Address**, check the **Portal address**. Change it if you like, using letters, numbers and single dashes, from 2 to 80 characters. 3. Select **Copy** to copy the full link. ![2 Portal address. 3 Copy.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106234612-04-address.png) > **Warning:** Changing the address changes every link to your portal, including links in emails you've already sent. Links with the old address may stop working. Want the portal on your own domain, such as `feedback.yourcompany.com`? See [Use your own domain](/rectify/help/a/44-use-your-own-domain). ## Save your changes When you change something, a bar appears at the bottom with **Unsaved changes**. Select **Save** to publish your changes to the portal, or **Discard** to drop them. The arrows in the bar undo and redo your last changes. ![Unsaved changes, Discard and Save.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106236507-05-save.png) If you try to leave the page before saving, Rectify asks **Leave without saving?**. Select **Keep editing** to go back and save. ## Check it worked After "Portal settings saved" appears, select **View portal** at the top of the page. Your portal opens in a new tab with your name, logo and menu. **Copy link** above the preview copies the link to the page you're previewing. ### It says "That portal address is already taken" Another portal already uses that address. Try a different one, for example with your company's name in it. ### It says "Pick an image under 5 MB" Make the image smaller or save it as a JPG, then upload it again. ## Read next - [Pick a portal theme and colours](/rectify/help/a/42-pick-a-portal-theme-and-colours) - [Control who can see the portal](/rectify/help/a/43-control-who-can-see-the-portal) - [Use your own domain](/rectify/help/a/44-use-your-own-domain) --- # Pick a portal theme and colours Collection: Portal and Help Center URL: https://app.rectify.so/rectify/help/a/42-pick-a-portal-theme-and-colours Choose your portal's theme, accent colour and default light or dark mode, or set your own brand colours. > **Note:** **Before you start.** Owners, Admins and Members can change the portal's look on every plan. Hiding "Powered by Rectify" needs the Launch plan or higher. ## Choose a theme and accent 1. In the sidebar, open **Publish**, then **Portal**, and open the **Brand** tab. 2. Under **Colors and theme**, pick a **Theme**: **Rectify** for warm, soft tones, **Classic** for crisp white and grey, or **Custom** for your own brand colours. 3. Pick an **Accent color**. Select one of the five swatches, or select the colour box at the end of the row to pick any colour or type its hex code. 4. Pick a **Default theme**: **System**, **Light** or **Dark**. 5. Select **Save** in the bar at the bottom. ![2 Theme. 3 Accent color. 4 Default theme.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106238910-01-colors.png) The theme colours the page, cards, text and borders. The accent colours buttons, links, votes and the current page in the menu. Rectify picks white or dark text on your buttons, whichever reads better on your accent. **Default theme** is the mode visitors see when they arrive. **System** follows their device's light or dark setting. Visitors can still switch with the sun and moon button in the portal header, and their browser remembers their choice. The preview on the left shows your changes before you save. With **System** picked, the preview follows the mode you use Rectify in. ## Use your own brand colours 1. On the **Brand** tab, pick the **Custom** theme. 2. Under **Custom colors**, choose **Light** or **Dark** to pick which set you're editing. 3. Set each colour: **Page background**, **Cards and menus**, **Hover and fills**, **Text**, **Muted text** and **Borders**. Select a colour box, or type a 6-digit hex code such as `#1F1E1D`. 4. Switch to the other mode and set its colours too. 5. Select **Save**. ![Custom colors, with the Light and Dark switch and six colours.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106240929-02-custom.png) When you first pick **Custom**, it starts with the colours of the theme you had. To start again from a ready-made set, select **Rectify** or **Classic** next to **Start from**. > **Tip:** Check both modes in the preview before you save. Visitors who prefer dark mode see your dark set, so keep its text easy to read on its background. ## Hide "Powered by Rectify" 1. Open the **Domain and more** tab. 2. Under **Powered by**, select **Hide** next to **Powered by Rectify**. 3. Select **Save**. ![2 Keep or Hide, next to Powered by Rectify.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106242839-03-powered-by.png) This removes the "Powered by Rectify" line from your portal's footer. It's included on Launch, Accelerate and Enterprise. On Idea and Build, the row shows **Upgrade**, and selecting **Hide** shows the plans that include it instead. ## Check it worked After "Portal settings saved" appears, select **View portal** at the top of the page. Your colours show on the portal straight away. Try the sun and moon button in the portal header to see the other mode. ### It says "Use a 6-digit hex color" Type the colour as `#` and six letters or numbers, such as `#F5362D`. Three-digit codes are expanded for you, and anything else goes back to the last colour. ### The preview looks different from my portal With **System** picked, the preview follows your own Rectify mode, while visitors see the mode their device uses. Use the sun and moon button on your portal to check both. ## Read next - [Set up your public portal](/rectify/help/a/41-set-up-your-public-portal) - [Use your own domain](/rectify/help/a/44-use-your-own-domain) --- # Control who can see the portal Collection: Portal and Help Center URL: https://app.rectify.so/rectify/help/a/43-control-who-can-see-the-portal Keep your portal public, make it private to your customers' email domains, or open it only to chosen segments. > **Note:** **Before you start.** Owners, Admins and Members can change who sees the portal, on every plan. Your team can always open your portal while signed in to Rectify, whatever you choose here. ## Choose who gets in 1. In the sidebar, open **Publish**, then **Portal**, and open the **Access** tab. 2. Under **Who can see it**, pick **Public**, **Private** or **Segments** next to **The portal**. 3. For a private or segment portal, enter the domains to let in under **Email domains let in**, separated by commas, such as `yourcompany.com, partner.com`. 4. Choose whether **Anyone can create a portal account**. 5. Select **Save** in the bar at the bottom. ![2 The portal. 3 Email domains let in. 4 Anyone can create a portal account.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106245459-01-access.png) For **Segments**, pick the segments under **Segments with access** as well. ## What each choice means | **Choice** | **Who gets in** | | --- | --- | | **Public** | Anyone with the link. Search engines can find it too, unless you turn that off. | | **Private** | Only people who sign in first. With email domains listed, only addresses on those domains. | | **Segments** | Only signed-in people in the segments you pick, or with an address on a domain you list. | Visitors sign in with a one-time code that Rectify emails them. There's no password. Until they sign in, a private portal shows nothing but a sign-in screen. People who sign in without access see "You do not have access to this portal". ## Who can create an account **Anyone can create a portal account** decides whether people Rectify doesn't know yet can sign in: - **On:** anyone can sign in and gets an account. On a private portal with email domains, that means anyone on those domains. This is the easiest way to let your whole company or a customer's team in. - **Off:** only people already in your contacts can sign in. Everyone else is told the portal is invite only. On a public portal, people can still read everything without signing in. When you switch a portal to **Private** without any email domains, Rectify turns this off for you. A private portal must list email domains or keep this switched off, so it never lets just anyone in. ## Limit a single page Some pages have their own reader setting, on top of who can see the portal: - **Changelog:** on the **Changelog** tab, under **Who can read it**, set **Readers** to **Everyone** or **Signed-in only**. **Signed-in only** covers the RSS feed too. - **Help Center:** on the **Help Center** tab, the same **Readers** setting decides whether visitors sign in before reading articles. ![Readers, under Who can read it, on the Changelog tab.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106247112-02-readers.png) Boards and roadmaps have their own visibility, set where you manage them under **Roadmap**. Turning a page off under **Pages in the menu** only hides it from the menu. Anyone with its link can still open it. ## Keep the portal out of search engines On the **Domain and more** tab, under **Search and sharing**, turn off **Let search engines index the portal**. It's on by default for public portals. A private or segment portal is never indexed, whatever this switch says. ![Let search engines index the portal.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106248751-03-indexing.png) ## Check it worked After saving, open your portal in a private browser window where you're not signed in to Rectify. A private portal should ask you to sign in. Sign in with an address on one of your listed domains to check you get in. ### It says "A private portal needs allowed email domains or invite-only sign-up" A private portal can't let just anyone sign in. Add your email domains under **Email domains let in**, or switch off **Anyone can create a portal account**, then save again. ### Someone on our domain can't get in Check their address is on a domain listed under **Email domains let in**, spelled the same way. If **Anyone can create a portal account** is off, only people already in your contacts can sign in, so switch it on to let in everyone on those domains. ### Visitors can still see a page I switched off Switching a page off under **Pages in the menu** only hides it from the menu. To stop people reading the changelog or Help Center, set its **Readers** to **Signed-in only**, or make the whole portal private. ## Read next - [Set up your public portal](/rectify/help/a/41-set-up-your-public-portal) - [Use your own domain](/rectify/help/a/44-use-your-own-domain) --- # Use your own domain Collection: Portal and Help Center URL: https://app.rectify.so/rectify/help/a/44-use-your-own-domain Open your portal at an address on your own domain, such as feedback.yourcompany.com, with HTTPS set up for you. > **Note:** **Before you start.** Custom domains are included on Launch, Accelerate and Enterprise. Only Owners and Admins can add, verify or remove one. You'll also need access to your domain's DNS settings, at the company where you bought the domain or host its DNS. One domain covers your whole organization. Each project's portal sits on its own path, so with `feedback.yourcompany.com` a portal opens at `feedback.yourcompany.com/your-portal-address`. Use a subdomain you don't use for anything else. ## Add your domain 1. Open **Organization settings**, then **Domain**. You can also get there from your portal settings: open **Domain and more** and select **Manage** next to **Custom domain**. 2. Under **Domain**, enter the subdomain you want, such as `feedback.yourcompany.com`. Leave out `https://`. 3. Select **Add**. ![2 Domain. 3 Add.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106251399-01-domain.png) Rectify shows the domain with the status **Waiting for DNS**, and lists the DNS records to create under **DNS records**. ## Create the DNS records Rectify shows two records, each with a **Type**, a **Host** and a **Value**: | **Type** | **What it does** | | --- | --- | | **CNAME** | Points your subdomain at Rectify. Its host is the first part of your domain, such as `feedback`. | | **TXT** | Proves you own the domain, so Rectify can set up HTTPS for it. | 1. Sign in to your domain provider and open the DNS settings for your domain. 2. Add a **CNAME** record with the **Host** and **Value** Rectify shows. Use the copy button next to each value so nothing is mistyped. 3. Add the **TXT** record the same way. 4. Save the records at your provider. Some providers add your domain to the end of the host by themselves. If yours does, enter only the part Rectify shows, such as `feedback`. ## Verify the domain 1. Go back to **Organization settings**, **Domain**. 2. Select **Verify**. When everything checks out, the status changes to **Verified** and HTTPS is set up for you. DNS changes can take up to 48 hours to reach everyone, so if it still says **Waiting for DNS**, wait a while and select **Verify** again. The status only updates when you select **Verify**. ## What changes once it's verified - Your portals open at your domain followed by their portal address. In your portal settings, **Domain and more** shows the new address. - Opening the domain on its own takes visitors straight to your portal. If your organization has several public portals, visitors pick one from a list. Private portals, and portals limited to segments, aren't listed. - Your `app.rectify.so` portal links keep working, so links you've already shared don't break. - Signing in on a custom domain may not work in incognito or private browsing windows. The public portal works as normal. ![Custom domain, with Manage, in your portal settings.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106253258-02-portal-row.png) ## Change or remove the domain - **Change it:** enter a new domain under **Domain**, select **Update**, then create the new DNS records and verify again. - **Remove it:** under **Remove domain**, select **Remove domain**, then **Remove** to confirm. Your organization stops opening at that address, and your portals stay at their `app.rectify.so` address. ## Check it worked When the status says **Verified**, select the open icon next to it, or go to your domain followed by your portal address. Your portal should open with a padlock in the browser's address bar. ### It says "Please enter a valid domain" Enter the domain only, such as `feedback.yourcompany.com`, without `https://`, `www.` or a path. ### It says "Domain already in use" Another Rectify organization is using that domain. Pick another subdomain, or remove it from the other organization first. ### It still says "Waiting for DNS" after a day Check both records at your provider against the ones Rectify shows, character by character. Make sure the CNAME host isn't doubled, such as `feedback.yourcompany.com.yourcompany.com`, and that no other record uses the same host. Then select **Verify** again. If there's a problem with the records, Rectify shows it in red under them. ### The page asks me to upgrade Custom domains are included on Launch, Accelerate and Enterprise. [Compare plans and what each one includes](/rectify/help/a/13-compare-plans) lists what each plan has. ### I don't see the Add button Only Owners and Admins can manage the domain. Ask one of them to add it. ## Read next - [Set up your public portal](/rectify/help/a/41-set-up-your-public-portal) - [Control who can see the portal](/rectify/help/a/43-control-who-can-see-the-portal) --- # Build your help center: collections and articles Collection: Portal and Help Center URL: https://app.rectify.so/rectify/help/a/45-build-your-help-center Group your help articles into collections, write an article and publish it to your help center. > **Note:** **Before you start.** Owners, Admins and Members can create collections, write articles and publish them. Only Owners and Admins can delete articles and collections, or restore them from **Deleted**. The free Idea plan includes 25 articles and Build includes 250. Launch, Accelerate and Enterprise have no limit. Drafts count too, until you delete them. Your help center lives on your portal at `/help`. Articles sit inside collections, and Quanta quotes your published articles when it answers customers in the widget. ## Create a collection 1. Open **Publish**, then **Help Center**. 2. Select **New collection** in the panel on the left. On an empty help center, **Let's GO!** opens the same window. 3. Pick an icon if you like, and type the collection's name. You can add a one-line description under it. 4. Under **Sits inside**, keep **Top level** to show the collection on the help center home, or pick a collection to put it inside. Collections go up to three levels deep. 5. Under **Who can read**, choose **Same as parent**, **Everyone**, **Signed-in only** or **Only your team**. The choice applies to every article inside unless an article sets its own. 6. Select **Create collection**. ![3 Name. 4 Sits inside. 5 Who can read. 6 Create collection.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106256028-01-new-collection.png) **Only your team** keeps a collection off the help center and the widget, and Quanta never uses it to answer customers. ## Write an article 1. Select **New article** in the panel. To start inside a collection, point at it, select **+** and then **New article**. 2. Type the title where it says **Article title**. 3. Add one line under the title. It shows in lists and search results. 4. Write the article. Type **/** for headings, callouts, code, images and more. Rectify saves as you type and shows **Saved** at the top. A new article saves once it has a collection. If you started from **New article** without one, open **Collection** in the bar on the right and pick one. ## Publish it 1. Select **Publish** at the top right. 2. Choose **Now**, or **Schedule** and pick a date and time. 3. Add a short note about what changed if you like. It shows in the article's version history. 4. Select **Publish now**, or the **Go live** button for a scheduled article. ![1 Publish. 2 Now or Schedule. 3 What changed. 4 Publish now.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106257713-02-publish.png) **Publish** stays greyed out until the article has a title and some text. ## Change a published article Edits to a published article are saved as **Unpublished changes**. Readers keep seeing the live version until you select **Publish changes** at the top right, then **Publish changes** again to confirm. To take an article down, open the same button at the top right and select **Take it off the help center**. For a scheduled article, select **Reschedule**, then **Cancel the schedule**. ## Organize your articles - **Find an article:** select a collection in the panel, or use the tabs: **All**, **Published**, **Unpublished changes**, **Drafts**, **Scheduled** and **Internal**. - **Change the order:** select a collection, keep the sort on **Manual**, then drag the articles into place. Drag collections in the panel the same way. - **Move an article:** open it and pick another collection under **Collection** in the bar on the right. - **Quick actions:** the menu at the end of each row has **Edit**, **Publish now** or **Publish changes**, **Move back to draft** and **Delete**. ![The article menu in the Integrations collection.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106259361-03-organize.png) A deleted article moves to **Deleted** at the bottom of the panel. You can restore it from there for 30 days. ## Check it worked Open a published article and select **View** at the top to see it on your help center, or use the open button next to **Help Center** at the top of the list. Within about a minute of publishing, the **Quanta index** button in the bar on the right shows **Indexed for Quanta**, and Quanta can quote the article. ### New article is greyed out Create a collection first. Articles always sit inside one. If you have collections, your plan's article limit is reached: delete articles you no longer need, or upgrade your plan. ### Someone else is editing the article Only one person edits an article at a time. You see who is editing, and you can read a copy. An Owner or Admin can select **Take over** to edit it instead. Next, [write with callouts, code groups, cards and more](/rectify/help/a/46-write-with-callouts-code-groups-and-cards), or let [Quanta draft and improve your articles](/rectify/help/a/47-draft-and-improve-articles-with-quanta). Moving from another tool? [Import your help articles](/rectify/help/a/48-import-help-articles). --- # Write with callouts, code groups, cards and more Collection: Portal and Help Center URL: https://app.rectify.so/rectify/help/a/46-write-with-callouts-code-groups-and-cards Add callouts, tabbed code, link cards, accordions, tables and images to your help articles from the / menu. > **Note:** **Before you start.** You need to be able to edit the article. Owners, Admins and Members can edit any article. The help article editor has blocks made for help content. They all come from one menu. ## Add a block 1. Start a new line in the article. 2. Type **/**. The menu opens. 3. Pick a block, or keep typing to filter the list, for example **/code**. ![1 Type / on a new line. The help article blocks sit under Advanced.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106262184-01-slash-menu.png) ## What each block is for | **Block** | **What it's for** | | --- | --- | | **Callout** | A note that stands out from the text | | **Code group** | Tabs with a snippet for each language or framework | | **Code block** | One snippet with syntax highlighting | | **Cards** | A grid of links to other articles or pages | | **Accordion** | A title that opens to show more, good for questions and answers | | **Columns** | Two or three columns side by side | | **Divider** | A line between sections | | **Table** | A table with editable cells | | **Image**, **Video** and **File** | A picture, a video or a download | | **Loom** | Record a Loom video and embed it | The menu also has **Heading 1** to **Heading 3**, lists, a check list, **Toggle List** and **Quote**. To add an emoji, type **:** and at least two letters of its name, like **:smile**. ## Write a code group 1. Type **/code group** and press Enter. The block starts with one tab. 2. Paste or type the first snippet. 3. Pick its language from the menu at the top of the block. The tab takes the language's name. 4. Select **Add tab** to add the next language, and repeat. Once there's more than one tab, select **+** to add another and pick each tab's language from the menu at the right. ![2 The snippet. 3 Its language. 4 Add a tab.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106264181-02-code-group.png) Readers switch between the tabs and copy the code with the copy button. A **Code block** works the same way with a single snippet. ## Add an accordion and cards 1. Type **/accordion** and press Enter. Write the question as the title, then open it with the arrow and write the answer inside. 2. Type **/cards** and press Enter. For each card, fill in the title, one line about where it goes, and the link: an article's address on your help center, like `/help/a/12-install`, or a full `https://` link. 3. Select **Add card** for more cards. Remove one with the **×** next to its title. ![1 An accordion. 2 Cards, with Add card below them.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106265815-04-cards-accordion.png) ## How readers see it On your help center, callouts get their colour and icon, code groups become tabs with a copy button, and images show with their caption. ![A callout, an image and a code group on the help center.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106267613-05-public-top.png) Accordions open with a click, and each card links to its page. ![A table, a warning callout, an open accordion and cards.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106269442-06-public-bottom.png) ## Check it worked Publish the article, then select **View** at the top of the editor. Every block shows as it will for your readers. ### Nothing happens when I type / The menu only opens while you can edit the article. If someone else is editing it, you're reading a copy. Wait until they finish, or ask an Owner or Admin to take over. ### A card goes to the wrong page Open the article you want to link to on your help center, copy its address, and paste it into the card's link. Next, let [Quanta draft and improve your articles](/rectify/help/a/47-draft-and-improve-articles-with-quanta), or go back to [building your help center](/rectify/help/a/45-build-your-help-center). --- # Draft and improve articles with Quanta Collection: Portal and Help Center URL: https://app.rectify.so/rectify/help/a/47-draft-and-improve-articles-with-quanta Let Quanta write a first draft from a prompt or a customer conversation, rewrite an article, or suggest its description and search details. > **Note:** **Before you start.** Quanta writes with your organization's AI provider key, or with the Rectify credits included in paid plans. Each draft, rewrite and suggestion uses them. You also need to be able to edit the article. Owners, Admins and Members can edit any article. Quanta lives in the bar on the right of the article editor. Nothing it writes goes live on its own: you read it, edit it and publish it like any other change. ## Draft an article 1. Open the article you want to write, or start a new one in a collection. 2. Select **Quanta** in the bar on the right of the editor. 3. On **Write**, pick what Quanta should work from, if you like: **A conversation** from your inbox, or **A customer question** nobody has answered yet. 4. Describe what the article should explain. A few lines are plenty. 5. Select **Draft**, or press ⌘ Enter (Ctrl Enter on Windows). ![2 Quanta. 3 Writing from a conversation. 4 What to explain. 5 Draft.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106272290-01-write.png) Quanta writes the title, the one-line description and the article while you watch. **Draft** replaces all three, so use it on a new or empty article. Select **Stop and keep this** to keep what it has written so far. ![Quanta's draft, saved as a draft and ready to edit.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106273955-02-drafted.png) ## Rewrite an article 1. Select **Quanta**, then **Rewrite**. 2. Pick **Improve** for clearer sentences and easier steps, **Shorten** to cut about a third, or **Fix tone** for a warm, direct support voice. 3. Or type exactly what to change and select **Rewrite**. ![2 Improve, Shorten or Fix tone. 3 Say what to change.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106276181-03-rewrite.png) A rewrite keeps the title and replaces the body. If you stop a rewrite partway, the article stays as it was. ## Get a description and search details 1. Select **Quanta**, then **Describe**. 2. Select **Generate**. Quanta reads the article and suggests the one-line description, the search title and the search description. When one fits, it also suggests a collection. 3. Select **Apply** to use them, or **Try again** for new suggestions. ![Quanta's suggestions on Describe. 3 Apply.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106277875-04-describe.png) The search title and description show under **Link and SEO** in the bar on the right. ## Check it worked When Quanta finishes, Rectify shows **Quanta drafted the article. Edit away.** or **Quanta rewrote the article.**, and the page says **Saved**. On a published article, the changes wait as **Unpublished changes** until you publish them. Read the result through before you publish: Quanta works only from your prompt, the source you picked and what's already in the article. ### Quanta shows "Add an AI provider key" instead of the tabs Your organization has no AI provider key and no Rectify credits left. An Owner or Admin can connect a provider under **Organization settings**, **AI providers**. ### Draft, Rewrite or Generate is greyed out **Draft** needs a prompt, a source or some text in the article. **Rewrite** and **Generate** need some text in the article first. ### "This article is longer than Quanta can rewrite in one go" Quanta rewrites up to about 12,000 characters of text at a time. Split the article in two, or rewrite it section by section. ### "Quanta could not write this. Try again." Something went wrong while Quanta was writing, and your article was left as it was. Wait a moment and try again. Next, [translate your help center](/rectify/help/a/49-translate-your-help-center), or [write with callouts, code groups, cards and more](/rectify/help/a/46-write-with-callouts-code-groups-and-cards). [Meet Quanta](/rectify/help/a/7-meet-quanta) covers everything else Quanta does. --- # Import articles from a website, Markdown or the Wiki Collection: Portal and Help Center URL: https://app.rectify.so/rectify/help/a/48-import-help-articles Bring existing help articles into your Help Center as drafts, from a public help site, a zip of Markdown files or pages in your Wiki. > **Note:** **Before you start.** Owners, Admins and Members can import. Every imported article counts toward your plan's Help Center article limit: 25 on Idea, 250 on Build, and no limit on Launch and above. Imports arrive as drafts, so readers see nothing until you publish them. Open **Help Center** under **Publish**, select **Import** at the top, and pick where your articles come from. ![1 Import, then one of the three sources.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106282259-01-import-menu.png) | **Source** | **Best for** | | --- | --- | | **From a help center URL** | Moving from another help center that's public on the web | | **Markdown zip** | Docs you keep as `.md` files, for example in a code repository | | **From the Wiki** | Team notes in your Wiki that customers should read too | ## Import from another help center 1. Select **Import**, then **From a help center URL**. 2. Under **Help center address**, enter the address of the help center's home page, starting with `https://`. 3. Under **How far to follow links**, pick how many clicks deep Rectify should go. **Two levels deep (usual for a help center)** suits most help centers. 4. Under **Put the drafts in**, pick a collection, or keep **A new collection named after the site**. 5. Optional: under **Article container**, enter a CSS selector for the part of each page that holds the article, like `.article-body`. Leave it empty and Rectify picks the largest block of text on the page. 6. Select **Start import**. ![2 Help center address. 3 How far to follow links. 4 Put the drafts in. 5 Article container. 6 Start import.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106284912-02-website.png) Rectify reads up to 300 pages, and only pages on that same site. Each page becomes one draft: its main heading becomes the title and its meta description becomes the article's description. Pages with too little text, like category lists, are skipped. Rectify also remembers each page's old path. If you later point your old help center's domain at your Rectify portal, links to the old pages open the new articles. Custom domains need the Launch plan or above. > **Tip:** Images in imported pages still load from your old site. Keep it online until you've replaced them, or add new images in the editor. ## Import a zip of Markdown files 1. Select **Import**, then **Markdown zip**. 2. Drop your zip on the box, or click it to choose the file. 3. Under **Put the drafts in**, pick the collection the articles should go into. 4. Select **Start import**. ![2 The zip. 3 Put the drafts in. 4 Start import.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106286735-03-markdown.png) How Rectify reads the zip: - Every `.md`, `.markdown` or `.mdx` file becomes one draft. Other files are ignored. - Each folder becomes a collection inside the one you picked. Collections nest up to three levels, so deeper folders are merged into the last level. - The title comes from `title:` in the file's front matter, then from a first `#` heading, then from the file name. `description:` in the front matter sets the description. - Image files in the zip aren't uploaded. An image written as `![Alt text](https://...)` on its own line keeps pointing to that address. - A zip can hold up to 500 Markdown files and 25 MB of Markdown. Files over 1 MB are skipped. A file like this one imports as "Export your data to CSV", with its description filled in: ```markdown --- title: Export your data to CSV description: Download every board, card and comment in your workspace as CSV files. --- Workspace admins can export everything in a workspace at any time. ``` ## Copy pages from the Wiki 1. Select **Import**, then **From the Wiki**. 2. Tick the pages you want to copy. 3. Under **Put the drafts in**, pick a collection. 4. Select **Copy** with the number of pages, for example **Copy 3 pages**. The pages stay in your Wiki. Later edits in the Wiki don't reach the Help Center copy, so update the article itself. You can copy up to 200 pages at a time. ## Check it worked While the import runs, the window shows its progress, like **Reading pages** or **Creating drafts**, with a count. You can close it, and the import keeps going. When it says **Done**, select **Show drafts**. ![Done, with the number of drafts created and Show drafts.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106288408-04-done.png) The list opens on the **Drafts** tab, with each new draft in the collection made from its folder. ![The new drafts on the Drafts tab.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106290089-05-drafts.png) Read each draft, fix anything the import missed, and select **Publish** when it's ready. To write notes for your team first and share them later, see [Keep team notes in the Wiki](/rectify/help/a/52-keep-team-notes-in-the-wiki). ### It says "That address is not reachable from imports" Rectify only imports from public sites. The address must open in a private browser window without signing in, and it can't be a local or private network address. ### It says "No article pages found at that address" Rectify found no page with enough article text. Start from the help center's home page, pick a deeper level under **How far to follow links**, or enter the CSS selector of the article area under **Article container**. ### Some pages are listed as "not enough article text" Those pages, like category lists or search pages, had less than a short paragraph of text in the article area, so they were skipped. If a real article was skipped, run the import again with its **Article container** selector. ### It says "Your plan has reached its help center article limit" The import stops when your plan has no room left, and the remaining pages aren't imported. While you're at the limit, the import options are greyed out. Upgrade your plan, or delete articles you no longer need. ### It says "The zip has no Markdown files in it" or "That file is not a zip archive" Zip the folder that holds your `.md` files and choose that `.zip` file. Other archive types don't work. --- # Translate your help center Collection: Portal and Help Center URL: https://app.rectify.so/rectify/help/a/49-translate-your-help-center Add languages to your help center, let Quanta draft each translation, then check it and publish it. > **Note:** **Before you start.** Owners, Admins and Members can add languages and publish translations. Anyone who can edit an article can ask Quanta to translate it and edit the translation. Quanta's translations use your AI provider key or the Rectify credits included in paid plans. You write each article in your default language. Every other language is a translation of it, and readers pick their language on the help center. ## Languages on each plan Your plan sets how many languages you can add on top of each project's default language. The count covers every project in your organization. | **Plan** | **Extra languages** | | --- | --- | | Idea (free) | 1 | | Build | 3 | | Launch | 10 | | Accelerate and Enterprise | Unlimited | For example, on Build you could add Spanish and German to one project and French to another. ## Add a language 1. Open **Publish**, then **Portal**, and select the **Help Center** tab. From the help center, the settings button at the top opens the same place. 2. Under **Languages**, select **Add a language** and pick one from the list. 3. Select the new language to write what your help center's home page says in it: **Heading**, **Intro** and **Search placeholder**. **Landing text missing** shows until you add a heading. 4. Select **Save**. ![2 Add a language. 3 Landing text for German.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106293123-01-languages.png) Under the list of languages you'll also find: - **Translate new versions automatically:** each time you publish an article, Quanta drafts it again in every extra language. A person still publishes each translation. Translations someone has edited by hand are left alone. - **Never translate these words:** product and feature names that stay exactly as written, like your brand name. Type a term and press Enter. ## Translate an article 1. Open the article. It needs to be published before a translation can go live. 2. Pick the language in the row at the top of the editor. 3. Select **Translate with Quanta**. You can also write the translation yourself. ![2 The language. 3 Translate with Quanta.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106294940-02-locale-bar.png) 4. Wait while it shows **Translating**. It usually takes under a minute. 5. Read the translation through and fix anything that's off. Your edits save as you type. 6. Select **Publish**. ![Quanta's Spanish draft, ready to check. 5 Publish.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106296414-03-translated.png) Readers see a **Machine translated** label on a translation Quanta wrote. Once you edit and publish it, the label goes away. ## Translate collection names 1. In the help center panel, open the menu next to a collection and select **Edit**. 2. Under **Other languages**, type the name and description in each language, or select **Translate all collections** to let Quanta translate the names of all your collections into that language at once. 3. Select **Save changes**. ![2 Translate all collections. 3 Save changes.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106298232-04-collection-names.png) A name you leave empty shows in your default language. ## Keep translations up to date When you publish a new version of an article, its translations show **Outdated**. Readers keep seeing the old translation until you update it. Open the language, select **Re-translate** or edit it, then publish it again. To find the gaps, select **Translations** above the article list and pick a language. The list shows published articles that have no translation in it yet. ![1 Translations. 2 Articles missing a German translation.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106300086-05-missing.png) ## Check it worked Open your help center and pick the language in the menu next to the article's details. An article with no translation shows in your default language. ![The Spanish article, with the language menu and the Machine translated label.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106302099-06-reader.png) ### "Translations can only go live once the article itself is published" Publish the article in your default language first, then publish the translation. ### "Translation failed" Quanta couldn't finish the translation, and the reason shows under the language name. Select **Re-translate** to try again. ### "Your plan does not include this many help center languages" Your organization has used all the extra languages on its plan, across all projects. Remove a language you don't need in another project, or upgrade your plan. ### Translate with Quanta is missing Your organization has no AI provider key and no Rectify credits left. An Owner or Admin can connect a provider under **Organization settings**, **AI providers**. You can still write the translation yourself. Next, [let readers ask Quanta](/rectify/help/a/50-let-readers-ask-quanta), or see [what each plan includes](/rectify/help/a/13-compare-plans). --- # Let readers ask Quanta in the help center Collection: Portal and Help Center URL: https://app.rectify.so/rectify/help/a/50-let-readers-ask-quanta Turn on Ask Quanta so readers get a short answer built only from your published articles, with the sources named. > **Note:** **Before you start.** Owners, Admins and Members can change this setting. Answers use your AI credits, which come with the Build plan and above, or your own AI provider key. Nothing is spent when no article matches the question. With **Ask Quanta in search** on, readers can type a question instead of a search. Quanta reads your published articles, writes a short answer and lists the articles it used. If your articles don't cover the question, it says so instead of guessing. ## Turn it on 1. Open **Portal** under **Publish**. 2. Select **Help Center** above the preview. The settings on the right switch to your Help Center. 3. Under **Quanta and AI tools**, turn on **Ask Quanta in search**. 4. Select **Save**. ![3 Ask Quanta in search. 4 Save.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106304934-01-setting.png) The name and picture readers see come from your widget. To change them, select **Change in Widget** next to **Name and picture**, then edit them on the widget's **Support** tab. ## What your readers see On your Help Center's home page, the search box gets two tabs, **Search** and **Ask Quanta**. Readers: 1. Select **Ask Quanta**. 2. Type their question. 3. Select **Ask**. ![1 Ask Quanta. 2 The question. 3 Ask.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106307043-02-ask-tab.png) The answer appears as it's written, with numbered links to the articles it came from. ![An answer with its source article.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106308735-03-answer.png) Readers can also ask from the search window on any Help Center page: they type a question and pick **Ask Quanta** in the results. If your widget shows the **Help** tab, the same **Ask Quanta** button appears there. When no article covers the question, readers see "I could not find that in the help articles. Try different words, or reach out to the team." with up to three articles that might help instead. ![No answer, with articles that might help instead.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106310554-04-no-answer.png) ## What Quanta answers from - Only published articles. Drafts and unpublished changes aren't used. - Only articles that reader can open. Articles for signed-in readers are only used for signed-in readers. - Never articles set to **Only your team**. Each question can be up to 500 characters. ## Check it worked Open your Help Center in a private window. If you see the **Ask Quanta** tab, ask a question one of your articles answers. To see every question people asked, open **Help Center**, then **Analytics**: **Answered by Quanta** counts the answers, and the **Searches** tab lists each question under **Asked Quanta**. Questions Quanta couldn't answer show up in **Content gaps**. See [Read Help Center analytics and fill content gaps](/rectify/help/a/51-read-help-center-analytics). ### The Ask Quanta tab doesn't show Check the setting is on and saved. The tab also stays hidden while your organization can't use AI: on the free Idea plan, or once your AI credits run out, connect your own AI provider under **Organization settings**, **AI providers**. ### Readers see "Too many questions in a row. Try again in a minute." Each internet address can ask 10 questions a minute. The reader can ask again a minute later. ### Readers see "This help center is busy answering questions. Try again in a minute." Your Help Center answers up to 120 questions a minute across all readers. The next minute works again. ### Readers see "This help center has answered all the questions it can for today. Try again tomorrow." Each Help Center takes up to 2,000 questions a day, counted from midnight UTC. Searching still works. ### Quanta keeps saying it couldn't find an answer Quanta only answers from what your articles say. Open **Content gaps** in analytics to see what people asked, then write the missing article. Quanta starts using it within a minute or two of publishing. --- # Read Help Center analytics and fill content gaps Collection: Portal and Help Center URL: https://app.rectify.so/rectify/help/a/51-read-help-center-analytics See which articles people read and trust, what they search for, and which questions your Help Center can't answer yet. > **Note:** **Before you start.** Everyone on your team who can open the project can see Help Center analytics, start articles from a gap and mark feedback as handled. ## Open analytics 1. Open **Help Center** under **Publish**. 2. Select **Analytics** at the top. 3. Pick the period in the top right: **7d**, **30d** or **90d**. ![The tabs, the period and the four numbers at the top of the Overview tab.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106314739-01-overview.png) The period applies to every tab except **Content gaps**, which always looks back over recent weeks. To download the numbers, select **Export** and pick **Articles CSV**, **Searches CSV** or **Feedback CSV**. ## Overview | **Card** | **What it counts** | | --- | --- | | **Reads** | Every time an article was opened, and how many different people opened articles. The line below splits reads between your portal and your widget. | | **Helpful** | The share of "Was this helpful?" votes that said yes, with the number of yes and no votes. | | **Searches** | Searches in your Help Center, the share that found nothing, and how many had no article. | | **Answered by Quanta** | Questions Quanta answered from your articles, out of all questions asked, and how often it cited an article. | Below the cards, **Reads per day** charts the period day by day (switch it to **Searches** to see searches instead), **Most read** ranks your articles, and **Where people read** compares the portal with the widget. A reader's search counts once, not once for every letter they type. If someone refines a search within a minute, Rectify keeps the search they settled on. ## Articles The **Articles** tab lists every article with its **Reads**, **Readers**, the **Portal / widget** split, how **Helpful** readers found it and how often it was **Cited by Quanta**. Select **Needs improving** to see only the articles readers struggle with: three or more votes, and fewer than half of them helpful. ![The Articles tab, with Needs improving.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106316404-02-articles.png) ## Searches The **Searches** tab lists what people searched for, with how often each search **Found nothing** and how often people **Asked Quanta**. Pick **No results** or **Asked Quanta** to narrow the list. A term with **Write article** next to it found nothing, or Quanta couldn't answer it. ![A search that found nothing, with Write article.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106318051-03-searches.png) ## Fill a content gap **Content gaps** groups the questions your Help Center couldn't answer by what they mean, so different wordings of the same question count as one gap. It collects three kinds: - **from search**: searches that found nothing. - **from Ask Quanta**: questions Quanta couldn't answer from your articles. - **in chat**: questions Quanta couldn't answer in your support chat. To answer one: 1. Select the **Content gaps** tab. 2. Next to the gap, select **Write article**. ![1 Content gaps. 2 Write article.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106319685-04-gaps.png) 3. A new article opens with the gap as its title. Rename it, write the answer and publish it. The list is worked out again every 10 minutes. Select **Recompute** to refresh it right away. ## Feedback When readers vote no, they can say what they were looking for. The **Feedback** tab shows those reasons. Filter by **With a reason**, **Unresolved**, **Not helpful** or **Everything**. Once you've fixed the article, select **Mark handled**. It leaves **Unresolved**, and **Reopen** brings it back. ![A reader's reason, with Mark handled.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106321123-05-feedback.png) ## Check it worked Open your Help Center in a private window, read an article and search for something. Reload analytics and your read and search are counted. ### Every card shows 0 Analytics count reads and searches in your public Help Center and in the widget's Help tab. Check the period, and that your articles are published. ### Answered by Quanta stays at 0 Readers can only ask Quanta when **Ask Quanta in search** is on. See [Let readers ask Quanta in the help center](/rectify/help/a/50-let-readers-ask-quanta). --- # Keep team notes in the Wiki Collection: Portal and Help Center URL: https://app.rectify.so/rectify/help/a/52-keep-team-notes-in-the-wiki Write pages for your team in each project's Wiki, nest them, keep some private, share one by link, and restore pages from the trash. > **Note:** **Before you start.** Every project has its own Wiki, and everyone on your team who can open the project can read and edit its pages. The Wiki is for your team: customers only see a page if you publish it. Use the Wiki for release checklists, meeting notes, how-tos for your team and drafts you're not ready to share. When a page should help customers too, copy it into your Help Center. ## Create a page 1. Open **Wiki** under **Publish**. 2. Select **New page** at the top of the Wiki list. In an empty Wiki, you can also select **Let's GO!**. ![1 Wiki under Publish. 2 New page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106323780-01-new-page.png) 3. Click **Untitled** and type the page's title. Press Enter when you're done. 4. Write the page. Type `/` to add headings, lists, checklists, tables, images and more. Everything saves as you type. There's no save button. To give the page a look, use **Add icon** to pick an emoji, and **Add cover** to add a banner image. A cover at least 1500 pixels wide looks best. Hover over a cover to **Change cover** or **Remove** it. ## Put pages inside other pages Hover over a page in the Wiki list and select **+** (**New page inside**). The new page sits under it, and the arrow next to a page shows or hides the pages inside it. ## Find a page Select **Search** at the top of the Wiki list and type part of a page's title. ## Keep a page private 1. Open the page. 2. Select the **⋮** menu at the top right. 3. Select **Make private**. A private page shows a lock in the Wiki list, and only you can see it. **Make public** shares it with your team again. Only the person who created a page can change this. ## Download a page Select the **⋮** menu at the top right, then **Download**, and pick **Plain Text (.txt)**, **Markdown (.md)** or **PDF (.pdf)**. ## Share a page by link 1. Open the page and select **Publish** at the top right. 2. Select **Publish**. 3. Select the copy button next to the link, and share it. Anyone with the link can read the page without signing in, so publish only what's fine to share. If the page is private, its link only opens for you, even while it's published. A globe next to **Publish** shows the page is live. To take it down, open **Publish** again and select **Unpublish**. ## Move a page to the trash Select **Move to trash** in the page's **⋮** menu, or in the **...** menu next to it in the Wiki list. Pages inside it go to the trash too. To bring one back, select **Trash** at the bottom of the Wiki list, then the **Restore** arrow next to the page. **Delete forever**, then **Confirm**, removes it for good. ## Turn a page into a help article To share a Wiki page with customers in your Help Center, open **Help Center**, select **Import**, then **From the Wiki**, and tick the page. Rectify copies it into a draft article, and the Wiki page stays as it is. See [Import articles from a website, Markdown or the Wiki](/rectify/help/a/48-import-help-articles). ## Check it worked Your new page appears in the Wiki list under **Pages**. Ask a teammate to open the Wiki: they see every page except private ones. ### A teammate can't see my page The page is private. Open it, select the **⋮** menu and select **Make public**. If they can't open the Wiki at all, they don't have access to the project. An Owner or Admin can add it under **Organization settings**, **Members**. ### I can't find Make private Only the person who created the page can make it private or public again. ### I deleted a page by mistake If you moved it to the trash, open **Trash** at the bottom of the Wiki list and select **Restore**. Pages you deleted forever can't be brought back. --- # Find people and accounts in Contacts Collection: Customers and analytics URL: https://app.rectify.so/rectify/help/a/105-contacts-and-companies How visitors become contacts, how companies are grouped, and how to search, filter and tidy up the list. > **Note:** **Before you start.** Contacts work on every plan. Everyone in the project can view, tag, merge and delete contacts. **Contacts** lists everyone the Rectify script has seen on your site, from first-time visitors to paying customers, and groups them into the companies they work for. ## Where contacts come from - **Visitors:** anyone who loads a page with the Rectify script becomes a contact straight away, even before you know who they are. - **Identified people:** once you tell Rectify who someone is, with a user ID or an email, their earlier visits join their named record. They can also identify themselves by signing in to your portal or by submitting a form with an email on your site. - **Discord:** when your project is connected to Discord, everyone who sends an idea or a bug report from your server, or upvotes or follows a request there, becomes a contact named after their Discord name. They have no email address. [Collect ideas and bug reports from Discord](/rectify/help/a/133-collect-ideas-and-bug-reports-from-discord) explains how. [Get contacts in: identify, the Contacts API and forms](/rectify/help/a/107-get-contacts-in-identify-the-contacts-api-and-forms) explains each way. ## Browse your contacts Open **Contacts** in the sidebar, under **Customers**. The **People** tab lists everyone, most recently seen first. The line above the list counts the total, how many are identified, and how many are anonymous visitors. ![The People tab with the count line, filters and search.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106607727-01-people.png) | **Column** | **What it shows** | | --- | --- | | **User** | Name and email, or **Anonymous** and a short ID. | | **Stage** | **Visitor**, **Lead**, **User**, **Customer** or **Churned**. | | **Score** | Their lead score, when there is one. | | **Signals** | Rage clicks, dead clicks and other friction in the last 7 days. | | **Last Seen** and **First Seen** | When they were last and first on your site. | **Stage** is worked out for you: - **Customer:** they or their company have a paid plan or monthly revenue (`plan` or `mrr` sent with identify). - **Churned:** their status or their company's status is churned or cancelled. - **User:** identified with a user ID. - **Lead:** only an email is known. - **Visitor:** not identified yet. Select a row to open the person's profile. [Read a contact's profile](/rectify/help/a/106-read-a-contacts-profile) walks through it. ## Search and filter 1. Type a name or email in **Search by name or email...** 2. Select **Filter** and pick one: - **Segment:** people in one of your saved segments. - **Country** or **Browser:** anyone who has visited from there or with it. - **Last seen:** **Today**, **Last 7 days**, **Last 30 days**, **Last 90 days** or **Custom range**. 3. To change a filter, select its pill. To clear everything, select **Reset**. ![2 The Filter menu.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106609616-02-filter.png) ## See companies Select the **Companies** tab. Rectify groups people into companies in this order: 1. The company ID you send with identify (`company.id`). 2. The company domain you send (`company.domain`). 3. The domain of their work email. Personal addresses such as Gmail and Outlook are left out. Each company shows its plan, monthly revenue (**MRR**), how many people you've seen from it and how many are identified, and when someone from it was last on your site. The list is sorted by MRR, and the line above it adds up the total. ![The Companies tab, sorted by MRR.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106611239-03-companies.png) Select a company to see its details and its people: - **MRR**, **Plan**, **Seats**, **Members**, **First seen** and **Last seen**. - **Stage:** **Prospect**, **Trial**, **Customer** or **Churned**. Rectify sets it from what you send, and you can change it. Once you change it, Rectify leaves your choice alone. - **Tags** and **Notes** for your team. - **Recount**, which counts the company's people again. - **People:** up to 25 people. When there are more, select **View all** to see everyone from the company on the **People** tab. ## Merge duplicates When the same email is split across more than one contact, a banner above the list reads, for example, **2 possible duplicates: the same email is split across multiple records.** 1. Select **Review**. 2. Select **Merge** next to each email. The identified record stays, and the others fold into it. Merging can't be undone. You can also merge two contacts by hand from a profile, with **Merge**. ## Delete a contact 1. Open the contact's profile. 2. Select **Delete**, then **Confirm delete**. Rectify erases the person and everything recorded about them, including their events on other devices and any emails waiting to be sent to them. This can't be undone. ## Check it worked The count line above **People** shows how many contacts you have. A company you send with identify appears on the **Companies** tab with its people. ### I see "No Contacts Yet" The Rectify script isn't on your site yet, or nobody has visited since you added it. Select **Let's GO!** for the install steps. ### A company shows up as its domain name Rectify grouped these people by their email domain because you didn't send a company name. Send `company.name` with identify and the name appears. ### Someone with a Gmail address has no company Personal email domains never form companies. Send a `company` with identify to put them in one. Read next: [Read a contact's profile](/rectify/help/a/106-read-a-contacts-profile). --- # Read a contact's profile Collection: Customers and analytics URL: https://app.rectify.so/rectify/help/a/106-read-a-contacts-profile Everything Rectify knows about one person in one place, from their company and friction to every page, feedback and chat. > **Note:** **Before you start.** Everyone in the project can open profiles, add tags and notes, and merge or delete contacts. A contact's profile gathers everything about one person: who they are, what they've done on your site, and every bug report, idea and chat they've sent. ## Open a profile 1. Open **Contacts** in the sidebar, under **Customers**. 2. Select a person in the **People** list. The profile opens on the right. Its address includes the person, so you can copy it from your browser and share it with a teammate. You can also reach a profile from **Activity**, with **Open profile** on any visit, or from a company's people list. ![A contact's profile, with friction, details and activity.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106614893-01-profile.png) ## The header - Their name, email and **Stage**. - **Score**, if they have one, and **First seen** and **Last seen**. - Their company, plan and monthly revenue, as you sent them with identify. ## Friction, last 7 days If the person ran into trouble in the last week, chips count it, for example **4 × Rage click** or **2 × JS error**. A contact with a lot of friction is often worth a message. ## Attributes | **Attribute** | **Where it comes from** | | --- | --- | | **Sessions**, **Page views** and **Time on site** | All their visits. | | **MRR**, **Revenue (30d)** and **Total revenue** | The `mrr` you send, or revenue events from your site. | | **Browser**, **OS**, **Device**, **Locale**, **Location** and **Timezone** | Their most recent visit. | | **First referrer**, **UTM source** and **UTM campaign** | Their first visit. | | **Last page** | The last page they opened. | Attributes with no value are hidden. If Rectify joined several browsers or records into this person, the count shows at the bottom of the section. When the person has an email, a line shows whether you can email them: **Contactable**, **Unsubscribed**, **No marketing** or **No product email**. ## Tags and notes 1. Under **Tags**, type a tag and press **Enter** or a comma. Select × on a tag to remove it. 2. Under **Notes**, write anything your team should know, then select **Save**. ![1 Tags. 2 Notes.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106617655-02-tags-notes.png) Tags and notes are shared with everyone in the project. You can segment on tags. ## Records from your own systems If you push custom objects, such as subscriptions or orders, the records that belong to this person show under their own heading. Select one to see its fields. [Add custom objects](/rectify/help/a/109-add-custom-objects) explains how. ## Activity **Activity** lists everything the person did, newest first: - Pages they viewed, what they clicked, forms, downloads and searches. - Friction such as rage clicks, dead clicks and errors. - When they identified themselves. - Feedback they sent, with its type and status, and **Replay** when a session replay is attached. - Support conversations, with their status. Scroll down to load older activity. ## Merge two contacts When one person shows up twice: 1. Open the profile you want to keep. 2. Select **Merge**. 3. Search for the duplicate by name or email, and select it. The duplicate's activity, feedback and conversations move into this profile, which keeps the earliest first-seen and latest last-seen dates. Merging happens as soon as you select the duplicate and can't be undone. ## Delete a contact Select **Delete**, then **Confirm delete**. Rectify erases the person and all their events. This can't be undone. ### The profile shows no activity The person was added from your server or a portal sign-in, and hasn't visited a page with the Rectify script since. Their activity appears after their next visit. ### Feedback from this person isn't on their profile Feedback joins a profile when its email matches the contact's email. Check that the person sent it with the same address. Read next: [Build segments](/rectify/help/a/108-build-segments). --- # Get contacts in: identify, the Contacts API and forms Collection: Customers and analytics URL: https://app.rectify.so/rectify/help/a/107-get-contacts-in-identify-the-contacts-api-and-forms Put names on your visitors from your site, send people and companies from your server, and let forms and portal sign-ins identify people for you. > **Note:** **Before you start.** Every visitor to a page with the Rectify script is already a contact. These steps tell Rectify who they are. You need the script on your site, and for the Contacts API, your project's write key. Analytics collection must be on (**Analytics**, **Settings**, switch at the top reads **On**). There are three ways to identify people. You can use any mix of them, and they all land on the same contact. | **Way** | **Best for** | | --- | --- | | **Identify in the browser** | Signed-in users of your app. Their earlier anonymous visits join their contact. | | **The Contacts API** | Syncing people and companies from your server, including people who never visit your site. | | **Forms and sign-ins** | Visitors who give you their email in a form on your site or sign in to your portal. | ## Identify in the browser Add `userInfo` to the Rectify snippet on pages where someone is signed in. Use your own user ID, which never changes, and their email and name: ```html ``` To add more about the person, such as their plan and their company, call `identify` once the page has loaded, for example after sign-in: ```js window.RectifyInstance?.identify('usr_1001', { email: 'jordan@northwind.com', name: 'Jordan Lee', plan: 'business', mrr: 1200, company: { id: 'acct_northwind', name: 'Northwind Labs', domain: 'northwind.com', plan: 'business', mrr: 1200, seats: 40, }, }); ``` - The first value is the user ID. Every other key is saved on the contact, and you can segment on **Plan** and **MRR**. - `company` puts the person in a company on the **Companies** tab. `id` matters most: people with the same company ID are grouped together. Send `status: 'trialing'` for a trial, or `status: 'canceled'` for a company that left. - Sending `plan` (anything but `free`) or `mrr` marks the contact as a **Customer**. > **Tip:** Call `identify` after the page has loaded, not in the same moment as the snippet. A call made before Rectify is ready is skipped. The `?.` keeps your page safe if the script hasn't loaded at all. For safety, identify calls only count from your own site: the project's **Website** address, its subdomains, or `localhost` while you test. If the project has no website set, any site counts. If you use the React, Vue, Nuxt, Svelte or Angular snippet, change `init('YOUR_PROJECT_ID')` to `init('YOUR_PROJECT_ID', { userId: ..., email: ..., name: ... })` to pass the same `userInfo`. ## Send people from your server The Contacts API creates or updates a contact by user ID or email. Get your project's write key from **Analytics**, **Settings**, **Setup**, under **Write Key**. Select the copy button next to it. ![The Write Key in the Setup tab of the analytics settings.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106620559-01-write-key.png) ```sh curl -X POST https://api.rectify.so/v1/contacts/identify \ -H "Authorization: Bearer YOUR_WRITE_KEY" \ -H "Content-Type: application/json" \ -d '{ "userId": "usr_1001", "email": "jordan@northwind.com", "name": "Jordan Lee", "company": { "id": "acct_northwind", "name": "Northwind Labs", "plan": "business", "mrr": 1200, "seats": 40 }, "attributes": { "plan": "business", "role": "admin" } }' ``` - Send `userId`, `email` or both. Rectify finds the contact by user ID first, then by email, and creates one if neither matches. - Put everything else about the person in `attributes`. Other top-level keys are ignored. - `company` replaces the company you sent before, so send all its fields each time. To send many people at once, post `{ "contacts": [ ... ] }` to `https://api.rectify.so/v1/contacts/bulk`, with up to 500 people per request. The API accepts up to 120 requests a minute. ## Let forms and sign-ins identify people These work without code: - **Forms on your site:** when someone submits a form with an email field, Rectify reads the email and name and identifies them. Switch this off under **Analytics**, **Settings**, **Capture**, **Identify people from forms**. - **Portal sign-in:** people who sign in to your portal become identified contacts with their email and name. - **Portal posts, votes and comments:** people who take part without signing in are added as contacts too. Feedback and chats from the widget don't create contacts on their own. They join a contact whose email matches. ## Check it worked Open **Contacts** and search for the person's name or email. They show with their **Stage**, and their profile shows **Identified themselves** in their activity. A company you sent appears on the **Companies** tab. ### The person still shows as Anonymous Check `identify` runs after the page has loaded and that you're testing on your project's website address or `localhost`. Then visit a page and wait a minute. ### The API says "Analytics write key required" or "Invalid analytics write key" Send the key as `Authorization: Bearer YOUR_WRITE_KEY`. If someone regenerated the key, copy the new one from **Write Key**. ### The API says "Analytics is disabled for this project" Analytics collection is paused for this project. An Owner or Admin can switch it back on at the top of **Analytics**, **Settings**. ### The API says "userId or email is required" Every contact needs a `userId`, an `email` or both. Read next: [Find people and accounts in Contacts](/rectify/help/a/105-contacts-and-companies). --- # Build segments Collection: Customers and analytics URL: https://app.rectify.so/rectify/help/a/108-build-segments Group contacts by who they are and what they've done, then use the group to filter contacts and target emails, surveys, popups and more. > **Note:** **Before you start.** Segments work on every plan. Everyone in the project can create, edit and delete them. A segment is a saved group of contacts, defined by conditions such as "on the Team plan" and "rage clicked in the last 7 days". Rectify keeps every segment up to date: people join and leave as their data changes, checked every 15 minutes. ## Create a segment 1. Open **Contacts** in the sidebar, under **Customers**. 2. On the **People** tab, select **Filter**, then **Segment**. 3. Select **New segment** at the bottom of the list. ![2 Filter, then Segment. 3 New segment.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106623155-01-new-segment.png) 4. Enter a **Name**, for example "Trial ending this week", and an optional **Description**. 5. Under **Who belongs to this segment**, select **Condition**. 6. Pick a field, then a condition, then enter or pick a value. 7. Add more conditions the same way. The count below updates as you go, for example **12 contacts match right now**. 8. Select **Create segment**. ![5 Condition. 6 Field, condition and value. 7 The live count. 8 Create segment.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106625314-02-builder.png) ## Combine conditions Each group of conditions is joined by **and** or **or**. Select the word at the top of the group to switch: - **and:** every condition must match. - **or:** any one condition can match. To mix them, select **Group** to add a group inside the first one. For example, "plan is team" **and** a group of "rage clicked" **or** "JavaScript error" finds paying users who hit trouble. Groups can go five levels deep, and a segment can have up to 50 conditions. ## Fields you can use | **Group** | **Fields** | | --- | --- | | **Contact** | Email, Name, User ID, Is identified, Tags, First seen, Last seen | | **Contact traits** | Plan, MRR | | **Company** | Company name, domain, plan, MRR, seats, members, lifecycle and tags | | **Device** | Browser, Operating system, Device type | | **Location** | Country, City | | **Acquisition** | Referrer, UTM source, UTM campaign | | **Behaviour** | Viewed page, Clicked, Submitted form, Downloaded file, Left for another site, Searched site, Identified, Custom event | | **Friction** | Rage clicked, Dead click, Bounced back, Scroll hunting, JavaScript error, Failed request | | **Custom events** | Each custom event your site sent in the last 30 days | Each custom object you've added gets its own group with the fields you marked for segments. [Add custom objects](/rectify/help/a/109-add-custom-objects) explains how. ## Conditions for each kind of field | **Field type** | **Conditions** | | --- | --- | | Text | **is**, **is not**, **contains**, **does not contain**, **starts with**, **is any of**, **is none of**, **is set**, **is not set** | | Number | **is**, **is not**, **is greater than**, **is less than**, **is set**, **is not set** | | Yes or no | **is**, **is not**, **is set**, **is not set** | | Date | **in the last**, **not in the last** (a number of days), **is before**, **is after** | | Behaviour and friction | **was performed**, **was not performed**, **happened more than**, **happened fewer than**, each **in the last** 1 to 365 days | Text matching ignores capitals. For **is any of** and **is none of**, separate values with commas. ## Use a segment Your segments show up wherever you choose an audience: - **Contacts:** **Filter**, **Segment** shows who's in it. - **Email campaigns:** send to a segment. Only people with an email receive it. - **Workflows:** start one when a contact enters or leaves a segment. - **Surveys** and **popups:** show them only to people in chosen segments. - **Help Center**, **changelog**, **roadmap** and **portal:** limit who can see an article, an entry, a roadmap or the whole portal. Anonymous visitors are never in a segment, so anything limited to segments is hidden from them. ## Edit or delete a segment Open **Filter**, then **Segment**, and hover over the segment: - Select the pencil to edit it, then **Save changes**. - Select the bin to delete it. It's deleted straight away, without a confirmation, and anything that used it no longer finds it. Every project starts with five ready-made segments: **Leads**, **New (7 days)**, **Active (30 days)**, **Dormant** and **Paying**. You can edit or delete them like your own. ## Check it worked Select **Filter**, **Segment** and pick your segment. The **People** list shows who's in it. Membership is first worked out right after you save, then every 15 minutes. ### It says "These fields are not recognised" A field in the segment no longer exists, for example a custom event that stopped arriving or a deleted custom object. Conditions on unknown fields match nobody. Remove them or pick another field. ### The count is 0 although I expected people Check that every condition can be true at once when the group uses **and**. Remember that only identified people have an email, a plan or a company. Read next: [Add custom objects](/rectify/help/a/109-add-custom-objects). --- # Add custom objects Collection: Customers and analytics URL: https://app.rectify.so/rectify/help/a/109-add-custom-objects Bring records from your own database, like subscriptions or orders, onto your contacts and segment on their fields. > **Note:** **Before you start.** Custom objects need the Build plan or higher. Each project can have 2 object types on Build, 5 on Launch, 20 on Accelerate and as many as you like on Enterprise. Everyone in the project can add and delete object types. Records are sent from your server with the project's write key. A custom object is a kind of record from your own systems, such as a **Subscription** or an **Order**. You define its fields once, send records from your backend, and each record shows on the profile of the person it belongs to. Fields you mark for segments become conditions in the segment builder. ## Define the object 1. Open **Contacts** in the sidebar, under **Customers**, and select the **Objects** tab. 2. Select **Let's GO!**, or **New Object** if you already have objects. 3. Enter a **Name** in the singular, such as "Subscription". **Plural** fills itself in. 4. Under **Fields**, enter a **Label** and pick a **Type** for each field: **Text**, **Number**, **Yes / no**, **Date** or **One of a list**. For **One of a list**, enter the allowed values, separated by commas. 5. Leave **Segment** on for fields you want to filter on, and switch on **Required** for fields every record must have. 6. Select **Field** (the plus button) to add more, up to 50. 7. Select **Create**. ![3 Name. 4 Fields. 5 Segment and Required. 7 Create.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106629779-01-create-object.png) The first field becomes each record's title. Select **Fill an example** to see a finished Subscription object, and the **How it works** tab for a walk-through. ## Send records from your server Send each record to the object's address with your write key. Find the key in **Analytics**, **Settings**, **Setup**, under **Write Key**, or copy a ready-made command from the **How it works** tab, which already includes it. ```sh curl -X POST https://api.rectify.so/v1/contacts/objects/subscription \ -H "Authorization: Bearer YOUR_WRITE_KEY" \ -H "Content-Type: application/json" \ -d '{ "externalId": "sub_8841", "email": "jordan@northwind.com", "data": { "plan": "business", "seats": 40, "renews_on": "2026-11-01" } }' ``` - **externalId** is your own ID for the record. Sending the same one again updates the record. - **email** or **userId** says which contact it belongs to. To attach it to a company instead, send **companyId** or **companyDomain**. - **data** holds the fields, by their keys: the label in lower case with spaces turned into underscores, such as `renews_on` for "Renews on". To send many records at once, post `{ "records": [ ... ] }` to the same address followed by `/bulk`, up to 500 per request. To remove a record, send a `DELETE` to the object's address followed by `/` and the record's externalId. ## See the records - On the **Objects** tab, expand an object to see its latest records. - On a contact's profile, each object has its own section with the person's records. - In the segment builder, each object has its own group of fields. ![An object's records on the Objects tab.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106632146-02-records.png) ## Delete an object On the **Objects** tab, select the bin next to the object, then **Delete**. Every record attached to it is removed too, and this can't be undone. Objects can't be edited after they're created. ## Check it worked After you send a record, the object's count on the **Objects** tab goes up, for example **3 fields · 12 records · 3 segmentable**, and the record shows on that person's profile. ### It says "Custom objects are not available on your plan" The free Idea plan doesn't include custom objects. [Compare plans](/rectify/help/a/13-compare-plans) shows what each plan includes. ### It says "Your plan allows 2 custom object types" You've reached your plan's number of object types. Delete one you don't use, or move to a bigger plan. ### The response says the record is "not attached to anyone" No contact or company matched the email, userId or company you sent. The record is stored but doesn't show on a profile or in segments. Check the contact exists, then send the record again. ### It says a field "is required" or "must be a number" Every **Required** field needs a value, and each value must match its type: a number for **Number**, true or false for **Yes / no**, a date for **Date**, and one of the allowed values for **One of a list**. Read next: [Get contacts in: identify, the Contacts API and forms](/rectify/help/a/107-get-contacts-in-identify-the-contacts-api-and-forms). --- # See what analytics captures on its own Collection: Customers and analytics URL: https://app.rectify.so/rectify/help/a/110-what-analytics-captures-on-its-own Every event the Rectify script records without any code from you, and how to switch each kind on or off. > **Note:** **Before you start.** Analytics uses the same Rectify script as the widget. If the widget is on your site, events are already coming in. Viewing the Analytics page needs the Build plan or higher. Only Owners and Admins can change what gets captured. Once the script is on a page, it records how people use it: pages, clicks, signs of frustration and errors. You don't write any tracking code for this. The same events power **Analytics**, **Activity**, **Heatmaps** and each contact's profile. ## What the script records Each row is a switch on the **Capture** tab. All of them start on except **Scroll depth**. | **Switch** | **What it records** | | --- | --- | | **Page views** | Every page someone opens, including page changes in single-page apps, and how far down they scrolled before leaving. | | **Clicks** | What people click and where on the element they clicked. | | **Frustration signals** | Rage clicks (three or more clicks on the same element within a second), dead clicks (a click that changes nothing), quick backs (leaving a page within 10 seconds and returning to the one before) and frantic scrolling. | | **Conversions** | File downloads, links to other sites and searches on your site (from a `q`, `s`, `search` or similar parameter in the address). | | **Errors** | JavaScript errors and failed network requests on your pages. | | **Form submissions** | That a form was sent, and which fields were filled in. Not what was typed. | | **Scroll depth** | A scroll event each time someone stops scrolling. Off by default because it's high volume. | Two more kinds are always recorded and have no switch: - **Page speed:** loading and responsiveness timings for each page (LCP, FCP, CLS, TTFB and INP). - **Element views:** when an element you've marked with the class `rectify-track-view` (or the attribute `data-rectify-track-view`) comes into view, once per page. ## What comes with every event - The page address and title, and the site the visitor came from. - Time on the page. - Browser, operating system, language and device type. Device type comes from the width of the window: up to 480 pixels is mobile, up to 1024 is tablet, wider is desktop. - Country and city, looked up from the visitor's IP address. The IP address itself isn't stored. - Campaign tags (`utm_source`, `utm_medium`, `utm_campaign`, `utm_term`, `utm_content`) when they're in the page address. Each browser tab counts as one session. A visitor keeps the same ID across visits on the same browser, and becomes a named contact when you identify them. ## Change what gets captured 1. Open **Analytics** in the sidebar, under **Customers**. 2. Select the gear button at the top of the page (**Settings**). ![2 The Settings button on the Analytics page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106636479-01-settings-button.png) 3. Select the **Capture** tab. 4. Switch each kind of event on or off under **What gets captured**. ![4 The switches under What gets captured.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106638293-02-capture-tab.png) Each switch saves as soon as you change it. Your site picks up the change the next time a page loads. ## Add your own events The automatic events cover how people move around. For actions that matter to your business, send your own from your page's code once the script has loaded: ```js window.RectifyInstance?.track('report_exported', { format: 'pdf' }); window.RectifyInstance?.revenue(49, 'USD', { plan: 'team' }); ``` `track` takes an event name and optional details. `revenue` records an amount and a currency, and feeds revenue goals. [Get contacts in: identify, the Contacts API and forms](/rectify/help/a/107-get-contacts-in-identify-the-contacts-api-and-forms) shows how to put names on visitors. ## Monthly events Each project can record your plan's monthly number of events: 500,000 on Build, 2 million on Launch, 10 million on Accelerate and no limit on Enterprise. The count resets on the first day of each month (UTC). Once a project reaches it, new events are turned away until the next month. ## Check it's working Open **Activity** in the sidebar and visit your site in another tab. Your visit appears within a minute. On the Analytics page, the top of **Settings** reads **Receiving events** while events are coming in, with the number that arrived in the last day. ### Nothing arrives from my site Check the script is on the page, and that the switch at the top of **Settings** reads **On**. Visitors whose browser sends Do Not Track aren't recorded while **Respect Do Not Track** is on. If your project used up its monthly events, nothing new is recorded until next month. ### Events I send from my server don't show up Rectify ignores traffic from bots and automated tools, and that includes many server-side HTTP clients. Requests sent with your project's write key are never filtered this way, so send server events with it, as [Send server events](/rectify/help/a/83-send-server-events) shows. ### Scroll maps work although Scroll depth is off Scroll maps use the scroll depth recorded when someone leaves a page, which comes with **Page views**. The **Scroll depth** switch only adds the extra scroll events. Read next: [Keep analytics private: masking, Do Not Track and form fields](/rectify/help/a/111-privacy-masking-do-not-track-and-form-fields). --- # Keep analytics private: masking, Do Not Track and form fields Collection: Customers and analytics URL: https://app.rectify.so/rectify/help/a/111-privacy-masking-do-not-track-and-form-fields Hide on-page text from analytics, respect Do Not Track, control what forms share, and keep parts of a page out of tracking altogether. > **Note:** **Before you start.** Only Owners and Admins can change these settings. They apply to every page the Rectify script runs on in this project. Rectify's analytics records what people do on your pages, not what they type. You decide how much text it keeps, whether it honours Do Not Track, and whether a submitted form can tell you who someone is. ## What analytics never keeps - **IP addresses.** The visitor's IP address is used to look up their country and city, then dropped. - **What people type.** A form event records which fields were filled in, not their values. Passwords and payment card fields are never read. - **Cookies.** The script sets no cookies. It keeps a visitor ID in the browser's local storage so return visits count as the same person. ## Change the privacy settings 1. Open **Analytics** in the sidebar, under **Customers**. 2. Select the gear button (**Settings**), then the **Capture** tab. 3. Under **Tracking privacy**, switch each setting on or off. ![3 The three settings under Tracking privacy.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106641150-01-tracking-privacy.png) | **Setting** | **Starts** | **What it does** | | --- | --- | --- | | **Mask all text** | Off | Records that an element was clicked, never the words on it. Search terms from your site's search are left out too. | | **Identify people from forms** | On | When someone submits a form with an email field, Rectify reads the email and name from it to recognise the visitor. | | **Respect Do Not Track** | On | Browsers with Do Not Track turned on send no analytics events. | Each setting saves as soon as you change it and applies the next time a page loads. > **Important:** **Identify people from forms** is the one setting that reads what someone typed: the email address and name in a form they submit. Turn it off if your forms collect emails you shouldn't link to visitors. ## Mask or skip parts of a page You can also mark elements in your own HTML. | **Add this** | **Effect** | | --- | --- | | `data-rectify-mask` attribute | Clicks still count, but the element's text is never sent. Heatmap snapshots show its text as asterisks. | | `rectify-no-capture` class | Nothing inside the element is tracked: no clicks, no frustration signals, no form events. Heatmap snapshots show it as an empty box of the same size. | ```html
$12,480.00
...
``` Page addresses and titles are still recorded for masked elements, so keep personal details out of your URLs and page titles. ## Share one field's value on purpose If you want a field's value with each form event, for example a plan picker, add `data-rectify-capture-value` to that field. Up to 200 characters are sent. Rectify still refuses fields that look sensitive: passwords, hidden fields, card and bank details, one-time codes, and fields named like a password, token, PIN, tax ID, passport or date of birth. ```html ``` ## Session replay and heatmap snapshots Bug reports can carry a replay of the visit, and heatmaps draw on a snapshot of your page. Both follow the masking settings for the widget, not the ones above. Open **Publish**, then **Widget**, and select **Privacy** to set **Mask all text**, **Mask all inputs** and the field types to hide. Passwords are always masked there. [Collect feedback and bug reports](/rectify/help/a/21-collect-feedback-and-bug-reports) explains replays. ## Check it's working Turn on **Mask all text**, open your site in a new tab and click a button. In **Activity**, the click shows the element without its words, for example **Clicked #export-pdf**. ### Someone with Do Not Track on still shows up in Activity The setting is read when the page loads. Check **Respect Do Not Track** is on, then reload the page in their browser. Visits recorded earlier stay in your data. ### A contact's name came from a newsletter form **Identify people from forms** was on. Turn it off to stop reading forms. People already identified this way stay identified. Read next: [See what analytics captures on its own](/rectify/help/a/110-what-analytics-captures-on-its-own). --- # Ask the analytics AI and read the daily brief Collection: Customers and analytics URL: https://app.rectify.so/rectify/help/a/112-ask-the-analytics-ai-and-read-the-daily-brief Read today's summary of your product data, then ask follow-up questions in plain English and get answers with charts. > **Note:** **Before you start.** Analytics needs the Build plan or higher. Everyone in the project can read the brief and ask questions. Answers run on your AI credits, or on your own AI provider if you've connected one under **Organization settings**, **AI providers**. Open **Analytics** in the sidebar, under **Customers**. The page opens on today's brief, four numbers for the week, and a box where you ask about anything in your event data. ![Today's brief, the week's numbers and the ask box.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106643901-01-analytics-home.png) ## Read today's brief **Today's brief** is a short summary that Quanta writes from your events: an opening line and a few bullet points on what changed, where people struggled, and anything unusual. When something looks off, it also checks your monitoring incidents and changelog. Under the brief are follow-up questions you can select to ask straight away. - The brief is written the first time someone opens Analytics each day (UTC), and everyone in the project sees the same one. - **Written at** shows when it was written. Select **Refresh** to write it again with the latest data. You can refresh once a minute. - Writing the brief uses AI credits, like any question. ## Read the week's numbers Below the brief, four numbers compare **This week against the week before**: the last 7 days, today included, against the 7 days before them. | **Number** | **What it counts** | | --- | --- | | **Visitors** | Different people who visited. | | **Page views** | Pages opened. | | **Avg. session** | Average time from the first to the last event in a visit. | | **Rage clicks** | Bursts of three or more quick clicks on the same element, with the page where they happened most. | The line above the brief shows how many people are on your site right now, with their latest events. ## Ask a question 1. Type your question in the box at the bottom, for example "Where are users dropping off in onboarding?" 2. To start from a ready-made question, select **Prompts** and pick one. Hover over a prompt to preview it. 3. Press **Enter** to send. **Shift+Enter** adds a new line. ![1 The ask box. 2 Prompts.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106646686-02-ask-box.png) The answer appears in a new chat and can include tables and charts. Keep asking follow-up questions in the same chat. You can attach up to 3 images or PDFs (10 MB each) with the paperclip button, and a message can be up to 2,000 characters. ## What you can ask The AI reads your events and the rest of your project. It can answer questions about: - **Traffic:** visitors, sessions, top pages, referrers, countries, devices and campaign tags. - **Funnels and retention:** drop-off between steps (events or page addresses) and how many people come back. - **Friction:** rage clicks, dead clicks, errors and failed requests, down to the element. - **Changes:** spikes and drops against the last 7 days, and whether a release or an incident lines up with them. - **Your customers:** contacts, companies and segments, survey answers and NPS, feedback, email campaigns and automations. - **Money:** revenue and goal conversions. It can also create a goal, an alert, a roadmap card or a changelog draft for you when you ask. ## Find a past chat Select **History** (the clock button at the top) to see your recent chats, newest first. Select one to open it. Your chats are private to you; teammates see their own. ## Export your events Select the download button at the top (**Export**), choose **CSV** or **JSON** and a **Date range** (**7d**, **30d**, **90d** or **6mo**), then select **Export CSV** or **Export JSON**. The file holds up to the 50,000 most recent events in that range. ## Check it worked The brief shows **Written at** with a time, and your question opens a chat where the answer streams in. ### The brief says "I could not finish today's brief." Select **Try again**. If it keeps failing, check that your organization has AI credits left or a connected AI provider under **Organization settings**, **AI providers**. ### It says "The brief was written a moment ago. Try again in a minute." You can refresh the brief once a minute. Wait a moment and select **Refresh** again. ### I see "Ask your product data anything" with an upgrade button Your organization is on the free Idea plan, which doesn't include analytics. [Upgrade, change or cancel your plan](/rectify/help/a/14-upgrade-change-or-cancel-your-plan) explains how to move up. Read next: [Set goals and alerts](/rectify/help/a/113-set-goals-and-alerts). --- # Set goals and alerts Collection: Customers and analytics URL: https://app.rectify.so/rectify/help/a/113-set-goals-and-alerts Count conversions for an event or a page, and get notified when traffic, revenue or any key metric crosses a line you set. > **Note:** **Before you start.** Goals and alerts need the Build plan or higher. Everyone in the project can add, pause and delete them. A **goal** counts a conversion each time a visitor fires an event or opens a page, for example a signup or a finished checkout. An **alert** watches a metric and tells you when it drops below or rises above a value. ## Add a goal 1. Open **Analytics** in the sidebar, under **Customers**. 2. Select the gear button (**Settings**), then the **Goals** tab. 3. Select **New goal**. 4. Enter a **Name**, for example "Signup conversion". 5. Under **Counts when**, pick **Event** or **URL path**, then enter the value: - **Event:** the exact name of an event your code sends, such as `user_signed_up`. Capitals matter. - **URL path:** part of the page address, such as `/checkout/success`. Any page whose address contains it counts. 6. Select **Create goal**. ![4 Name. 5 Counts when. 6 Create goal.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106652009-01-new-goal.png) The goal appears in the list with its conversions over the last 30 days: - **Conversions:** how many times the event fired or the page was opened. - **Converting:** the share of all visitors in those 30 days who converted at least once. - **Revenue:** shown when the matching events carry an amount, for example from `RectifyInstance.revenue()`. ![The goals list with conversions for each goal.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106653832-02-goals-list.png) You can also ask the analytics AI, for example "Create a conversion goal for my signup event". ## Add an alert 1. In **Settings**, select the **Alerts** tab. 2. Select **New alert**. 3. Enter a **Name**, for example "Traffic drop warning". It's shown in the notification. 4. Pick the **Metric**: **Pageviews**, **Unique visitors**, **Custom events**, **Revenue** or **Sessions**. 5. Under **Fires when**, pick **drops below**, **rises above** or **changes by %**, and enter the value. 6. To also get an email, switch on **Email**. 7. Select **Create alert**. ![4 Metric. 5 Fires when. 6 Email. 7 Create alert.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106656035-03-new-alert.png) ## How alerts are checked - Rectify checks every alert every 15 minutes, against the last 24 hours. - **changes by %** compares the last 24 hours with the 24 hours before, in either direction. It doesn't fire when the earlier period had nothing. - After an alert fires, it stays quiet for 12 hours, even if the metric is still past the line. - Everyone who can open the project gets an in-app notification. - With **Email** on, every Owner and Admin in your organization also gets an email titled **Analytics alert:** followed by the alert's name. - If Quanta's check-ins are on for the project, the alert also appears in Quanta's Project Report chat. ## Pause or delete In the **Alerts** tab, use the switch on an alert to pause it (**Pause this alert**) or turn it back on (**Resume this alert**). To remove a goal or an alert, select its delete button and confirm with **Delete**. A deleted goal stops counting straight away. Goals and alerts can't be edited. To change one, delete it and add a new one. ## Check it worked A new goal shows its conversions in the **Goals** tab as soon as it's created, counting back 30 days. A new alert shows in the **Alerts** tab with its metric and line, for example "Unique visitors drops below 80 · in-app and email". ### My event goal shows 0 conversions The event name must match exactly, including capitals, and it must be an event you send with `track`. Built-in events like clicks don't count. Check the name in **Activity**, under **Category**, **Custom**. ### My URL path goal counts too much A URL path goal counts every page whose address contains the text. Make it more specific, for example `/checkout/success` instead of `/checkout`. ### I didn't get the email Alert emails go to Owners and Admins only, and only when **Email** is on for that alert. Members get the in-app notification. Read next: [Ask the analytics AI and read the daily brief](/rectify/help/a/112-ask-the-analytics-ai-and-read-the-daily-brief). --- # Read heatmaps Collection: Customers and analytics URL: https://app.rectify.so/rectify/help/a/114-read-heatmaps See where people click and how far they scroll on any page, drawn on a snapshot of the page itself. > **Note:** **Before you start.** Heatmaps come from the Rectify script, so it needs to be live on your site for a while. Everyone in the project can open them. A heatmap shows what people do on one page of your site: where they click, which elements frustrate them, and how far down they get. Rectify draws it on a snapshot of your real page. ## Open a page's heatmap 1. Open **Heatmaps** in the sidebar, under **Customers**. Your busiest page with clicks opens first. 2. To pick another page, select the page button at the top left and choose from the list. Pages are ranked by views, with their clicks next to them. Type to filter the list. ![2 The page list, ranked by views.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106658972-01-page-picker.png) 3. Pick **Clicks** or **Scroll depth**. 4. Choose a window: **7 days**, **14 days** or **30 days**. 5. To see one kind of device, select **Desktop**, **Tablet** or **Mobile** next to **All**. ![3 Clicks or Scroll depth. 4 The time window. 5 The device filter.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106661006-02-controls.png) Pages whose addresses differ only by an ID, for example `/orders/1042` and `/orders/1043`, are combined into one entry. The address ignores anything after `?` or `#`. ## Read the click map ![The click map on the page, with the busiest elements listed on the right.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106662668-03-click-map.png) - **The glow** shows where clicks landed inside each element, from blue (**Fewer**) to red (**More**). - An amber border marks an element with rage clicks or dead clicks. - Hover over an element to see its clicks, its share of the page's clicks, and its rage and dead clicks. The panel on the right sums up the page: | **Number** | **What it means** | | --- | --- | | **Pageviews** | Times the page was loaded in the window. | | **Clicks** | Clicks recorded with a position on the page. | | **Clicks / view** | Average clicks per pageview. Very low usually means the page is read, not used. | | **Rage clicks** | Three or more clicks on the same element within a second. | | **Dead clicks** | Clicks on something clickable that produced no visible response. | | **Exits measured** | Visits that left a scroll depth when they ended. | Under **Elements**, the most-clicked elements are listed with problems first. Select one to scroll the page to it. Elements are named after their `data-rectify-id`, `data-testid` or ID, so giving key buttons one of these makes the list easier to read. ## Read the scroll map Pick **Scroll depth**. The page darkens from top to bottom as fewer people reach each part, from **Everyone** to **Few visitors**. Lines mark where 75% of visitors are still reading, where half have stopped, and where only 25% remain. The panel shows **Visitors reaching** each 10% of the page. ![The scroll map of the pricing page, with the share of visitors reaching each part.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106664782-04-scroll-map.png) ## How fresh it is - New clicks reach the click map within about an hour. - The page snapshot is captured at most once a day per page and device, the first time someone visits it with the script live. If the page has changed since, a few elements may no longer match, and the footer says how many. - Parts of the page you've marked as private stay private in the snapshot: text marked `data-rectify-mask` shows as asterisks, and `rectify-no-capture` areas show as empty boxes. [Keep analytics private: masking, Do Not Track and form fields](/rectify/help/a/111-privacy-masking-do-not-track-and-form-fields) explains both. ## Check it worked The footer under the page reads, for example, **312 clicks across 24 elements** in click mode or **48 exits measured** in scroll mode. ### "No page snapshot yet" The snapshot is taken when someone visits the page with the script live. Check that **Record sessions** or **Capture technical logs** is on under **Publish**, **Widget**, **Privacy**: the snapshot is taken by the same recorder. ### "No element clicks recorded" The page has views but no clicks in this window and device. Try **30 days** or **All** devices, and check that **Clicks** is on in the analytics **Capture** settings. ### "The captured page snapshot could not be rendered." The snapshot was damaged or too large to draw. A fresh one is captured the next time someone visits the page with the script live. ### The numbers in the page list differ from the panel The list counts clicks as they arrive, while the map counts them once an hour and includes rage and dead clicks. They line up after the next hourly update. Read next: [Watch the activity feed](/rectify/help/a/115-watch-the-activity-feed). --- # Watch the activity feed Collection: Customers and analytics URL: https://app.rectify.so/rectify/help/a/115-watch-the-activity-feed Follow visits on your site as they happen, grouped by person and session, and filter for friction, errors or conversions. > **Note:** **Before you start.** Activity shows the events the Rectify script records on your site. Everyone in the project can open it. **Activity** is a live feed of what people do on your site. Each row is one visit by one person, with the pages they saw, how long they stayed and any trouble they ran into. ## Open the feed Open **Activity** in the sidebar, under **Customers**. ![The activity feed, grouped by day and visit.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106667570-01-feed.png) Four numbers at the top cover the last 24 hours: | **Number** | **What it shows** | | --- | --- | | **Events · 24h** | Every event from every visitor. | | **Friction · 24h** | Rage clicks, dead clicks, quick backs and frantic scrolling, and their share of all events. | | **Busiest event** | The most frequent kind of event. | | **Event types seen** | How many different kinds of event arrived. | ## Read a visit Visits are grouped by day (**Today**, **Yesterday**, then the date). Each row shows: - The person's name or email, or **Visitor** and a short ID for someone you haven't identified, with an **Anonymous** label. - Their email, country and browser. - Up to three of the pages they visited. - A count of friction events, if there were any. - When the visit happened, how many events it had and how long it lasted. Events from the same person count as one visit until there's a 30-minute gap. 1. Select a row to open its timeline: every event in order, with its time and page. 2. Select **Open profile** to see everything about that person. ![1 An expanded visit. 2 Open profile.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106669191-02-visit.png) Events read in plain words, for example **Clicked "Invite teammates"**, **Downloaded export.csv** or **Identified themselves**. ## Filter the feed - **Everything** or **Friction:** **Friction** keeps only signs of trouble, including JavaScript errors and failed requests. - **Category:** on **Everything**, pick one or more of **Navigation**, **Interaction**, **Friction**, **Errors**, **Conversions**, **Identity** and **Custom**. Each shows how many arrived in the last 24 hours. - **Audience:** **Identified** or **Anonymous** people. - **Search:** type part of a page address, a page title or a custom event name. Select **Reset** to clear every filter. ![The Everything and Friction tabs, Category, Audience and search.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106672238-03-filters.png) ## Live updates New events appear at the top every 10 seconds while the toggle reads **Live**. Select it to switch to **Paused** and keep the feed still while you read. If you've scrolled down, new events wait behind a **new events** button at the top instead of moving the rows. Scroll down to load older events. The feed goes back as far as your plan keeps analytics history. ## Check it's working Visit your own site in another tab. Within a minute your visit appears at the top of the feed. ### "No Activity Yet" The script isn't sending events yet. Add it to your site, or check it's live, then visit a page. Select **Let's GO!** for the install steps. ### "Nothing matches these filters" No events in the feed match your category, audience and search together. Select **Reset filters**. ### I can't find a visitor by name Search looks at page addresses, page titles and custom event names, not people. To find a person, use **Contacts**. Read next: [Read a contact's profile](/rectify/help/a/106-read-a-contacts-profile). --- # Send from your own domain Collection: Messaging and surveys URL: https://app.rectify.so/rectify/help/a/97-send-from-your-own-domain Connect your Resend account so campaigns, and if you like your other project emails, go out from an address on your own domain. > **Note:** **Before you start.** Only Owners and Admins can connect an email provider. You need a Resend account with your sending domain added and verified there. Resend is the email provider campaigns use for now. Campaigns always send from your own email account, so your domain, your sending reputation and your sending limits stay yours. Until a provider is connected, starting a campaign asks you to connect one. ![Connect an email provider, shown when you start a campaign before connecting one.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106561854-01-connect-dialog.png) ## Get your domain ready in Resend 1. Sign in at resend.com. 2. Under **Domains**, add your sending domain and finish verifying it. 3. Under **API Keys**, create a key with **Full access**. Rectify uses a full access key to set up bounce and spam complaint tracking in your Resend account. With a sending-only key, emails still go out, but bounces and complaints aren't tracked. ## Connect Resend 1. In your project, open **Project settings**, then **Integrations**. 2. Select **Resend**. 3. Paste your **API Key**. 4. Enter the **From Email**. It must be on a domain you verified in Resend. 5. Optional: enter a **From Name**, for example your company name. Without one, Rectify uses the name from your email branding. 6. Select **Connect**. ![3 API Key. 4 From Email. 5 From Name. 6 Connect.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106563478-02-resend-form.png) Rectify checks the key and makes sure the domain of your **From Email** is added and verified in your Resend account. When it says "Resend connected successfully", you're ready to send. You can also reach it from **Messaging**: open the **Email settings** tab and select **Connect** next to Resend under **Sending**. ![Sending on the Email settings tab, with Connect next to Resend.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106565095-03-sending.png) ## Check how campaigns send Open **Messaging**, then the **Email settings** tab. Under **Sending**: | **Setting** | **What it does** | | --- | --- | | **Email provider** | Shows Resend as **Connected**, with the name and address campaigns send from. | | **Reply-to** | Where replies go. Leave it empty and replies go to the address campaigns send from. | | **Time zone** | Used when you schedule a campaign, and for the click times in **Analytics**. | Each campaign can still use its own **From name** and **Reply-to** in its **Email settings**. ## Send your other emails from your domain Rectify sends your project's other emails itself unless you switch them over. Once Resend is connected: 1. Open **Project settings**, then **Email notifications**, and select the **General** tab. 2. Under **Sending domain**, switch on what should go out from your address: - **Changelog and Quanta emails**: changelog updates to subscribers, and emails Quanta sends for you. - **Project emails**: feedback, chat, mentions and portal sign-in codes sent to your users. If Resend fails, these fall back to Rectify so sign-ins keep working. ## Disconnect Resend Open **Project settings**, **Integrations**, **Resend**, and select **Disconnect** under **Disconnect Resend**. Rectify removes the key and the bounce tracking it set up. A campaign that's sending when you disconnect pauses, and you can resume it once a provider is connected again. ## Troubleshooting ### It says "Invalid Resend API key format. Should start with re_." Copy the whole key from Resend again. Resend keys start with `re_`. ### It says "Resend did not accept this API key. Check it and try again." The key was deleted or mistyped. Create a new key in Resend and paste it. ### It says the domain "is not added to your Resend account" or "is not verified in Resend yet" The **From Email** must be on a domain in your Resend account that has finished verifying. Add or verify it under **Domains** in Resend, then select **Connect** again. ### It says "Bounces and spam complaints are not tracked" Rectify couldn't set up tracking in your Resend account, usually because the key has sending access only. Disconnect Resend and connect it again with a **Full access** key. ## Read next - [Write emails](/rectify/help/a/98-write-emails) - [Send a campaign: audience, schedule and A/B test](/rectify/help/a/99-send-a-campaign) --- # Write emails Collection: Messaging and surveys URL: https://app.rectify.so/rectify/help/a/98-write-emails Start a campaign email from a template, a blank page, your own HTML or a Quanta draft, then build it with blocks and send yourself a test. > **Note:** **Before you start.** Campaign emails go out through your own Resend account, so an Owner or Admin has to connect it first. [Send from your own domain](/rectify/help/a/97-send-from-your-own-domain) shows how. Owners, Admins and Members can write and edit drafts. Drafting with Quanta needs an AI provider or Rectify credits. ## Start a new email 1. In your project, open **Customers**, then **Messaging**. 2. On the **Campaigns** tab, select **New campaign**. 3. Select **Email**. The other two choices open Surveys and the widget's popup messages. 4. In **New email**, enter a **Campaign name**. Only your team sees it. 5. Write the **Subject line** and the **Preview text**, the line most inboxes show after the subject. **In the inbox** shows how they look together. 6. Optional: change the **From name**. It's the name people see the email from. 7. Select **Continue**. 8. Choose how to start. You can change everything afterwards. ![The ways to start an email: Design with Quanta, Start from scratch, Paste your own HTML and the templates.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106568058-01-start.png) | **Start with** | **What you get** | | --- | --- | | **Design with Quanta** | Describe the email and select **Draft it**. Quanta writes it as blocks you can edit. The chips under the box, such as **Monthly product update**, fill in an example to start from. | | **Start from scratch** | A blank email with your logo, a heading, a text block and your default signature. | | **Paste your own HTML** | Your own HTML, cleaned for email. Scripts, forms and tracking pixels are removed, and Rectify adds the unsubscribe footer. | | A template | **Product update**, **Feature announcement**, **Newsletter**, **Welcome**, **Feedback request**, **Changelog digest** or **Personal note**. Templates your team saved show first. | ## Build the email The builder has three parts: the blocks you can add on the left, the email in the middle and the settings of the selected block on the right. 1. To add a block, select it under **Add a block**. It goes below the block you selected. 2. To change a block, select it in the email or under **In this email**. Its settings open on the right. 3. To greet people by name, select **Variable** in a Text block and pick **First name**. Rectify fills it in for each person. 4. Select **Save** at the bottom, or press Cmd S. ![1 Add a block. 2 The selected block. 3 Variable.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106569774-02-builder.png) Point at a block in the email to move, copy or delete it. You can also drag it by its handle, or select it and press Alt and the up or down arrow. Undo and redo sit above the email, and **Desktop** and **Phone** show how it looks on each. | **Block** | **What it's for** | | --- | --- | | **Heading** | A short title | | **Text** | Paragraphs, lists and links | | **Button** | One clear next step | | **Image** | A picture, with an optional link | | **Video** | A preview that opens a YouTube, Vimeo or Loom video | | **Changelog** | Entries from your published changelog | | **Two columns** | Two short points side by side | | **Steps** | A numbered how-to | | **Quote** | Something a customer said | | **Signature** | Who the email is from | | **HTML** | Your own HTML, cleaned for email | | **Divider** | A thin line | | **Spacer** | Space between blocks | | **Logo** | Your logo from **Email settings** | An email can have up to 80 blocks. ### Personalise it | **Variable** | **Fills in** | | --- | --- | | `{{first_name}}` | **First name** | | `{{last_name}}` | **Last name** | | `{{name}}` | **Full name** | | `{{email}}` | **Email** | | `{{company}}` | **Company** | When someone has no first name, they see "there". To change that word, open **Email settings** above the email and fill in **When there is no first name, say**. ### Let Quanta help - **Rewrite** on a Text block offers **Make it shorter**, **Make it friendlier**, **Make it clearer** and **Fix spelling and grammar**. - **Ask Quanta** above the email rewrites the whole email from what you ask. Undo brings back the old version. - **Suggest** next to **Subject line** in **Email settings** offers subject lines based on the email. ### Settings for this email Select **Email settings** above the email to change things for this email only: the **Subject line**, **Preview text**, **From name** and **Reply-to**, the **Design**, the **Footer and personalisation**, and **Tracking and delivery** (**Track opens**, **Track clicks**, **Add UTM tags to links** and **Skip people emailed in the last 3 days**). To reuse the email later, select **Save as template** at the bottom. Your whole team sees it when they start a new email. The blocks and the look are saved, not the audience. ## Preview it and send a test 1. Select **Preview** at the bottom. If you have changes that aren't saved, it says **Save and preview**. 2. To see the email with someone's details filled in, pick them under **Preview as**. 3. Select **Send a test to me**, or enter a teammate's address and select **Send**. ![2 Preview as. 3 Send a test to me, or a teammate's address.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106571411-03-test.png) 4. Look through **Checks**. Select **Fix** next to anything marked, and Rectify takes you to it. Tests can only go to people in your organization, and they never count in the results. The subject starts with "[Test]". When a subject line test is on, you get one test for each subject. When the email is ready, select **Choose audience**. [Send a campaign](/rectify/help/a/99-send-a-campaign) covers the rest. ## Set the look for every email Owners and Admins can set the starting look for every campaign. Open **Messaging**, then the **Email settings** tab. ![The Look settings on the Email settings tab.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106573094-04-look.png) | **Section** | **What you set** | | --- | --- | | **Look** | **Logo**, **Accent**, **Background**, **Width**, **Font**, **Corners**, and whether to keep the **Rectify branding** line. The logo and accent are shared with Email notifications. | | **Signatures** | Names, roles and photos to sign emails with. One is the **Default**. | | **Footer** | **Postal address**, **Footer text**, a **"View in browser" link** and the word used when there is no first name. The unsubscribe link is always added. | | **Saved templates** | Rename or delete the templates your team saved. | Select **Save** in the bar at the bottom. Hiding the Rectify branding needs the Launch plan or higher. ## Troubleshooting ### Selecting Email opens "Connect an email provider" No email provider is connected to this project. An Owner or Admin can select **Connect Resend**. [Send from your own domain](/rectify/help/a/97-send-from-your-own-domain) walks through it. ### Checks says "Add your postal address, email laws require it in every marketing email" Open **Email settings** above the email and fill in **Postal address**, or set it once for every email on the **Email settings** tab. ### Checks says "Unknown variable" A variable is misspelled. Use one from the **Variable** menu, written exactly as it shows, for example `{{first_name}}`. ### It says "Test emails can only go to people on your team" Tests go only to people in your organization. Send it to your own address or a teammate's. ## Read next - [Send a campaign: audience, schedule and A/B test](/rectify/help/a/99-send-a-campaign) - [Send from your own domain](/rectify/help/a/97-send-from-your-own-domain) --- # Send a campaign: audience, schedule and A/B test Collection: Messaging and surveys URL: https://app.rectify.so/rectify/help/a/99-send-a-campaign Pick who gets your email, send it now or at a set time, and test two subject lines before everyone gets the winner. > **Note:** **Before you start.** Only Owners and Admins can send or schedule a campaign. Your project needs a connected email provider ([Send from your own domain](/rectify/help/a/97-send-from-your-own-domain)), and your email needs a subject line and a postal address in its footer. Subject line tests and sending in each person's time zone need the Launch plan or higher. ## Choose who gets it 1. Open your email and select **Audience and send** in the steps at the top, or **Choose audience** after the preview. 2. To send to everyone, select **All contacts**. That's everyone with an email address who can get marketing email. 3. To send to some people, select **Segments and roadmap voters** and tick one or more groups. Someone in more than one group gets the email once. 4. Optional: open **Leave people out** and tick the segments that shouldn't get it. ![2 All contacts. 3 Segments and roadmap voters, with Active (30 days) ticked. 4 Leave people out.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106575873-01-audience.png) The line under the page shows how many people it sends to, and how many are left out. Not sure who to pick? Select **Suggest an audience** and Quanta suggests groups from the email, your segments and your roadmap votes. Select **Use this audience** to take them. Rectify always leaves these people out: - People who unsubscribed from marketing emails. - Addresses that bounced or marked an earlier email as spam, and addresses your team added to **Suppressions**. - People who already got three marketing or product emails from this project in the last 24 hours. - With **Skip people emailed in the last 3 days** on in the email's settings, people who got another campaign in the last three days. ## Choose when it goes out 1. Under **When**, select **Schedule**. To send right away, leave it on **Send now**. 2. Pick a time: **Tomorrow**, **Tuesday**, **Next Monday**, or **Pick a date** and a time. When Rectify knows when your contacts click most, it suggests that day instead of Tuesday, marked **most clicks**. 3. Choose the **Time zone**: your project's time zone, or **Each person's**. ![1 Schedule. 2 Tomorrow at 10:00. 3 Each person's time zone.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106577692-02-schedule.png) Your project's time zone comes from **Time zone** on the **Email settings** tab. With **Each person's**, everyone gets it at that time where they are. People with no known time zone get it at that time in your project's time zone, and anyone whose time has already passed gets it straight away. A scheduled time must be at least a minute ahead and within the next year. ## Test two subject lines A subject line test sends two subject lines to small groups first, then sends the winner to everyone else. To turn it on, switch on **Test a second subject line** when you create the email, or in **Email settings** above the email, and write **Subject line B**. The test then shows on the audience page: 1. Under **Pick the winner by**, choose **Clicks** or **Opens**. 2. Under **Each subject goes to**, pick 5%, 10%, 15%, 20% or 25% of the audience. It starts at 10%. 3. Under **Then wait**, pick how long to wait before choosing: 1, 2, 4, 8, 12 or 24 hours. It starts at 4. ![1 Pick the winner by. 2 Each subject goes to. 3 Then wait.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106579210-03-subject-test.png) The line under the test says how many people get each subject and how many get the winner. A subject line test can't send in each person's time zone, and it needs open or click tracking on, whichever picks the winner. ## Send it 1. Select **Send now**, or **Schedule for** and the time, at the bottom right. 2. Check the **Subject**, **From**, **To** and **When**. 3. Select **Send now** or **Schedule**. If you haven't sent yourself a test of this version, Rectify reminds you and offers **Send a test first**. A scheduled campaign shows as **Scheduled** under **Campaigns**. To change it, open the menu on its row and select **Cancel schedule**. It goes back to being a draft and nothing is sent. While a campaign sends, you can pause it or select **Stop sending** from its report. Emails already sent stay sent. ## Troubleshooting ### The Send now button is greyed out Point at it to see why. The most common reasons: - "Only owners and admins can send campaigns. Ask one to send it." - "Connect an email provider in Email settings first. Campaigns send from your own account." - "Add a subject line first." or "Write subject line B, or turn the test off." - "Pick who gets it first." or "Nobody in this audience can get email." - "Pick a time in the future." ### It says "A subject line test cannot send in each person's time zone" Pick your project's time zone, or turn the subject line test off. ### It says "Subject line tests are on the Launch plan and above" Subject line tests and sending in each person's time zone need the Launch plan or higher. [Upgrade, change or cancel your plan](/rectify/help/a/14-upgrade-change-or-cancel-your-plan) explains how to move up. ### Sending stops with a message about the postal address or another check Rectify runs the same checks as **Preview and test** before it sends. Open **Preview and test**, select **Fix** next to the problem, and try again. ## Read next - [Read campaign results](/rectify/help/a/100-read-campaign-results) - [Write emails](/rectify/help/a/98-write-emails) --- # Read campaign results Collection: Messaging and surveys URL: https://app.rectify.so/rectify/help/a/100-read-campaign-results See who got your campaign, who opened and clicked it, what bounced, and how all your campaigns are doing over time. > **Note:** **Before you start.** Everyone on your team can read campaign results. A report fills in once the campaign starts sending. Only Owners and Admins can pause or stop a campaign from its report. ## Open a campaign's report 1. In your project, open **Customers**, then **Messaging**. 2. On the **Campaigns** tab, select a campaign that has been sent, or is sending. Drafts and scheduled campaigns open in the editor instead. A report for a campaign that hasn't started says "Not sent yet". The top of the report shows when it was sent, how many people it went to, who it's from and its subject. **View email** shows the email as people got it, and **Duplicate** starts a new draft from it. ## What the numbers mean | **Number** | **What it counts** | | --- | --- | | **Delivered** | Emails that reached an inbox, out of those sent. | | **Opened** | People who opened it at least once. Opens by machines, such as privacy features that load every email, are left out. | | **Clicked** | People who clicked a link at least once. Clicks by link scanners are left out. | | **Clicks** | Every click on every link. | | **Bounced** | Emails that couldn't be delivered. These addresses are left out of every later send. | | **Unsubscribed** | People who unsubscribed from this email, as a share of those it reached. | | **Spam complaints** | People who marked it as spam. Keep it under 0.1%. Gmail doesn't report these. | | **Clicks on a phone** | The share of clicks that came from a phone. | A dash means opens or clicks weren't tracked for this campaign. You switch tracking on or off under **Tracking and delivery** in the email's **Email settings**. ## Below the numbers | **Section** | **What it shows** | | --- | --- | | **Opens and clicks, first 24 hours** | Opens and clicks hour by hour after sending. | | **From send to click** | How many were sent, delivered, opened and clicked. | | **Clicks by link** | Clicks on each link, and how many people clicked it. | | **What Quanta sees** | Select **Read the results** for a short summary from Quanta, or **Ask Quanta** to talk it through. | | **Subject line test** | Each subject's open or click rate, and which one won. | | **By group** | Open and click rates for each segment you sent to, when you picked more than one. | | **Not sent to** | People in the audience who didn't get it, and why. For example, they unsubscribed or already got three emails that day. | When a campaign has finished and some people didn't open it, **What Quanta sees** offers **Resend to the** number **who did not open**. It makes a new draft for just those people, so you can change the subject before sending it. ## See each person Under **Recipients**, every person is listed with their status, opens, clicks and last activity. - Filter by **All**, **Opened**, **Not opened**, **Clicked**, **Bounced**, **Unsubscribed** or **Skipped**. - Search by name or email. - Select someone to see their timeline, from sent to clicked, and the other campaigns they got. **Open contact** takes you to their profile. - **Export CSV** downloads the list with each person's status, opens, clicks, times, device and the reason they were skipped. Person by person results are kept as long as your plan keeps analytics history: 30 days on Idea, 90 on Build, 180 on Launch, a year on Accelerate and two years on Enterprise. After that, the report keeps its totals. ## See all campaigns together Open the **Analytics** tab in **Messaging** and pick **7 days**, **30 days** or **90 days**. ![1 The Analytics tab, with the totals, sent campaigns, click times and list health.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106582082-01-analytics.png) | **Part** | **What it shows** | | --- | --- | | **Emails delivered**, **Open rate**, **Click rate**, **Unsubscribes** | Totals for the campaigns sent in that period. | | Sent campaigns | Each campaign's recipients, open rate, click rate and unsubscribes. Select one to open its report. | | **When people click** | Clicks by day and time over the last 90 days. Rectify suggests the busiest time when you schedule. | | **List health** | How many contacts **Can get email**, and how many unsubscribed, bounced, complained or were removed by your team. | ## Troubleshooting ### Opened and Clicked show a dash Opens or clicks weren't tracked for this campaign. Switch on **Track opens** and **Track clicks** in the email's **Email settings** before you send the next one. ### Bounced and Spam complaints stay at 0 Rectify may not be able to hear back from your Resend account. Open **Messaging**, **Email settings**. If it says "Bounces and spam complaints are not tracked", reconnect Resend with a **Full access** key. [Send from your own domain](/rectify/help/a/97-send-from-your-own-domain) shows how. ### The report says "Person by person results were cleared" The campaign is older than your plan keeps analytics history. The totals stay. ## Read next - [Send a campaign: audience, schedule and A/B test](/rectify/help/a/99-send-a-campaign) - [Write emails](/rectify/help/a/98-write-emails) --- # Create a survey Collection: Messaging and surveys URL: https://app.rectify.so/rectify/help/a/101-create-a-survey Ask Quanta to draft a survey, or start from a template or a blank page, then name it and put it live on your site. > **Note:** **Before you start.** Owners, Admins and Members can create, edit, pause and delete surveys, on every plan. Drafting with Quanta needs an AI provider or Rectify credits. Surveys show on your site through the Rectify script, so [install it](/rectify/help/a/5-install-the-rectify-widget) first. ## Start a survey 1. In your project, open **Customers**, then **Surveys**. The **New survey** tab opens. 2. Describe what you want to learn and press Enter, for example "Ask people why they cancel, right on the cancel page". Quanta drafts the questions and where the survey shows. You can also pick a template under **Or start from a template**, or select **Start blank**. ![2 Describe what you want to learn. The templates are below.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106584665-01-start.png) 3. Check the draft. To change it, type what you want in the box, or select a suggestion such as **Make it shorter**, **Add a follow-up question** or **Only known customers**. 4. Select **Open in editor**. ![3 Make it shorter. 4 Open in editor.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106586557-02-draft.png) The conversation isn't saved. If you leave the page before saving, Rectify asks whether to save the draft first. | **Template** | **Questions** | | --- | --- | | **NPS** | How likely people are to recommend you, from 0 to 10, then why | | **Support satisfaction** | How the help was, with faces from 1 to 5, then what could be better | | **Cancellation reasons** | Why they're cancelling, from four choices, then what would change their mind | | **Onboarding check-in** | How easy setting up was, from 1 to 7, then what almost stopped them | | **Feature feedback** | How useful a feature is, in stars, then what's missing | | **Product-market fit** | How they'd feel without your product, then the main benefit | ## Name it and put it live 1. Enter a **Name**. Only your team sees it. 2. Choose the **Status**: **Draft** keeps it off your site, **Live** shows it to visitors as soon as you save. ![1 Name. 2 Status.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106588179-03-editor.png) 3. Select **Create survey** in the bar at the bottom. To save it as a draft, leave the status on **Draft**. A survey needs at least one question to go live. Before you save, go through the other tabs: | **Tab** | **What you set** | | --- | --- | | **Questions** | The questions, in order. See [Survey question types](/rectify/help/a/102-survey-question-types). | | **Audience** | Everyone, known contacts or anonymous visitors, and segments. | | **Placement** | Where on the screen it sits, which pages it shows on, and which devices. | | **Look** | The **Primary**, **Text** and **Background** colours, the **Corner radius**, and **Progress** shown as a **Bar**, a **Count** or **None**. | | **Schedule** | What makes it appear, how often, and the dates it runs. | | **Success** | The thank-you screen: an icon, a **Heading** and a **Message**. | The preview next to the editor shows the survey as visitors will see it. [Choose who sees a survey and when](/rectify/help/a/103-choose-who-sees-a-survey-and-when) covers the **Audience**, **Placement** and **Schedule** tabs. Hiding the "Powered by Rectify" line under the survey, on the **Look** tab, needs the Launch plan or higher. ## Pause, change or delete a survey Open the **Surveys** tab to see every survey with how many times it was shown and completed. ![Pause and More actions on a survey in the list.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106589822-04-list.png) - To stop showing a live survey, select the pause button. Select it again to start showing it again. - To change a survey, open **More actions** and select **Edit**, change it, then select **Save**. - To delete a survey, open **More actions** and select **Delete**. Its answers are deleted with it, and this can't be undone. | **Status** | **What it means** | | --- | --- | | **Draft** | Not shown on your site. | | **Live** | Shown to visitors who match. The list says **Active**. | | **Scheduled** | Live, with a start date that hasn't come yet. | | **Paused** | Not shown until you start it again. | | **Finished** | Not shown any more. A live survey also shows as finished once its end date passes. The list says **Completed**. | ## Troubleshooting ### It says "Add a question before this can go live" Add at least one question on the **Questions** tab, or save it as a **Draft**. ### It says "Add an AI provider key in Settings, or top up AI credits, before drafting a survey with Quanta" Your organization has no AI key and no Rectify credits left. Pick a template or select **Start blank** instead, or ask an Owner or Admin to connect a provider under **Organization settings**, **AI providers**. ### The survey doesn't show on my site Check that the survey is **Live**, that the Rectify script is on the page, and that the page and device match the **Placement** tab. Someone who already answered it isn't asked again, so test in a private browser window. ## Read next - [Survey question types](/rectify/help/a/102-survey-question-types) - [Choose who sees a survey and when](/rectify/help/a/103-choose-who-sees-a-survey-and-when) - [Read survey results](/rectify/help/a/104-read-survey-results) --- # Survey question types Collection: Messaging and surveys URL: https://app.rectify.so/rectify/help/a/102-survey-question-types The nine kinds of question a survey can ask, the settings each one has, and how skip logic sends people to a different question. > **Note:** **Before you start.** Owners, Admins and Members can edit survey questions, on every plan. A survey can have up to 20 questions, though one or two get far more answers than five. ## Add a question 1. Open the survey in the editor and select the **Questions** tab. 2. Under **Add a question**, select the kind of question you want. It's added at the end. ![The nine kinds of question under Add a question.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106592393-01-add.png) 3. Write the question. You can add a supporting line under it. 4. Switch on **Required** if people must answer before moving on. New questions start optional. 5. Select **Save** in the bar at the bottom. Questions are asked top to bottom. Drag a question by its handle to move it. To change a question's kind, pick another one at the top of the question. Its settings start over, but the question text stays. ## The question types | **Type** | **What visitors see** | **Settings** | | --- | --- | --- | | **NPS** | A scale from 0 to 10 for how likely they are to recommend you | Labels for both ends | | **Satisfaction** | A rating from 1 to 5 | **Numbers** or **Faces**, labels for both ends | | **Effort** | A scale from 1 to 7 for how easy something was | Labels for both ends. They start as "Very difficult" and "Very easy". | | **Rating** | Your own scale | **Numbers**, **Stars**, **Hearts** or **Faces**, the size of the scale, labels for both ends | | **Yes / No** | Two answers | **Buttons**, with your own wording for each, or **Thumbs** | | **Pick one** | A list where they choose one option | The options, at least two | | **Pick many** | A list where they choose several options | The options, at least two | | **Free text** | A box to type in | **Placeholder text** | | **Email** | A box for an email address, checked as they type | **Placeholder text** | Labels for the ends of a scale can be up to 60 characters, and a question up to 300. ### Set the scale of a Rating question | **Style** | **Scale** | | --- | --- | | **Numbers** | From 0 or 1, up to any number from 2 to 10. It starts at 1 to 5. | | **Stars** or **Hearts** | From 3 to 10 stars or hearts. | | **Faces** | Always five faces, from 1 to 5. | ### Add options to a choice question Select **Option** to add another choice. A **Pick one** or **Pick many** question needs at least two, and a survey keeps the first 20. ## Skip people to another question Skip logic sends people to a different question, or ends the survey, depending on their answer. It works on **NPS**, **Satisfaction**, **Effort**, **Rating**, **Yes / No** and **Pick one** questions, but not on the last question. 1. On the question, select **Skip logic**. 2. Choose how to compare the answer: **is**, **is not**, **is at least**, **is at most** or **is anything**. Choice questions offer **is**, **is not** and **is anything**. 3. Enter the answer, or pick it from the options. 4. Under **go to**, pick a later question or **Finish the survey**. ![A rule that sends people who give 4 stars or more straight to question 3. 1 Skip logic. 2 How to compare. 3 The answer. 4 Where to go.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106594006-02-question.png) You can add up to 10 rules to a question. They're checked top to bottom, and the first one that matches wins. When no rule matches, the survey moves to the next question. If you move or delete questions, check the rules again. A rule keeps pointing at the question it had. ## Troubleshooting ### It says "Choice questions need at least two options" Add another option with **Option**, or change the question to **Free text**. ### It says "The scale must end above where it starts" On a **Rating** question with **Numbers**, set the end of the scale higher than the start. ### It says "Every question needs text" One of the questions is empty. Write the question, or delete it. ## Read next - [Create a survey](/rectify/help/a/101-create-a-survey) - [Choose who sees a survey and when](/rectify/help/a/103-choose-who-sees-a-survey-and-when) --- # Choose who sees a survey and when Collection: Messaging and surveys URL: https://app.rectify.so/rectify/help/a/103-choose-who-sees-a-survey-and-when Target a survey by audience and segment, limit it to some pages and devices, and decide what makes it appear and how often. > **Note:** **Before you start.** Owners, Admins and Members can change who sees a survey, on every plan. Surveys show through the Rectify script, so it needs to be on your site. Open the survey in the editor. Each of the three tabs below has one card of settings. Select **Save** in the bar at the bottom when you're done. Select **Guide** at the top of the page to see a line of help under each setting. ## Choose who sees it On the **Audience** tab, under **Who sees it**: ![The Audience tab.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106596714-01-audience.png) | **Setting** | **What it does** | | --- | --- | | **Audience** | **Everyone**, **Known contacts** (visitors you've identified, with an email or a user ID) or **Anonymous only**. | | **Limit to segments** | Shows it only to people in at least one of the segments you select. None selected means no segment filter. This shows once your project has segments. | Anonymous visitors are never in a segment, so don't combine **Anonymous only** with segments. Nobody would see the survey. ## Choose where it shows On the **Placement** tab, under **Where it shows**: 1. Under **Only on these pages**, enter the pages it can show on, separated by commas. Empty means every page. 2. Under **Never on these pages**, enter the pages it must not show on. This wins over the list above. 3. Under **Devices**, select **Desktop**, **Tablet** or **Mobile**. None selected means all devices. ![1 Only on these pages. 2 Never on these pages. 3 Devices.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106598427-02-placement.png) **Position** sets where the card sits: **Bottom right**, **Bottom left**, **Top right**, **Top left**, **Centre**, **Centre left**, **Centre right** or **Top bar**. Pages are matched on the part of the address after your domain, including anything after a `?`: - `/pricing` matches only `/pricing`, not `/pricing?plan=pro`. - `*` matches anything within one part of the address. `/docs/*` matches `/docs/install` but not `/docs/widget/install`. - `**` matches across parts. `/docs/**` matches both. - Start a pattern with `https://` to match the full address instead. Capital letters don't matter. The device comes from the width of the visitor's screen: up to 480 pixels is a phone, up to 1024 is a tablet, and wider is a desktop. ## Choose when it shows and how often On the **Schedule** tab, under **When and how often**: 1. Under **Show it when**, pick what makes the survey appear. Select **Trigger** to add up to three. The first one to happen shows the survey. 2. **Ask each person only once** is on for new surveys. Switch it off to let the survey come back, then set how often. 3. Optional: set **Starts** and **Ends** to run it between two dates. Leave them as **Any time** to run it whenever it's live. ![1 Show it when. 2 Ask each person only once. 3 Starts and Ends.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106599849-03-schedule.png) | **Trigger** | **When the survey shows** | | --- | --- | | **Straight away** | As the page loads, or after the number of seconds you enter. | | **After a delay** | After the visitor has been on the page for the number of seconds you enter. New surveys start at 10. | | **After scrolling** | Once the visitor scrolls down the percentage of the page you enter. It never shows on a page too short to scroll. | | **When leaving** | When the pointer moves up out of the page, towards the address bar or close button. | | **After frustration** | After **Rage clicks**, **Dead clicks**, **Frantic scrolling** or an **Immediate bounce**, or any of them. This needs frustration signals from analytics, which must be on for your project. | With **Ask each person only once** off: - **Days before asking again**: how long before it can show again. 0 means it can come back on the next visit. - **Max times per person**: how many times one person can see it. 0 means no limit. It starts at 1, so raise it to let the survey come back. Someone who answers a survey is never asked it again. **Ends** runs through the end of that day. ## How visitors see surveys - A survey shows at most once per page load. When several surveys match, the first one found shows. - While a survey is on screen, popup messages wait. - Surveys show even when you hide the widget's launcher, but not when the widget is switched off. ## Troubleshooting ### Nobody sees the survey Check that it's **Live**, that today is between **Starts** and **Ends**, and that the page matches **Only on these pages**. With **Known contacts**, the visitor must be identified. Someone who already answered it, or already saw it as many times as you allow, isn't shown it again. ### It says "This trigger will never fire until you turn analytics on" **After frustration** needs analytics on for your project. Pick another trigger, or turn analytics on. ## Read next - [Create a survey](/rectify/help/a/101-create-a-survey) - [Read survey results](/rectify/help/a/104-read-survey-results) --- # Read survey results Collection: Messaging and surveys URL: https://app.rectify.so/rectify/help/a/104-read-survey-results See how many people saw and finished a survey, your NPS and satisfaction scores, every answer, and export the responses as a CSV. > **Note:** **Before you start.** Everyone on your team can read and export survey results, on every plan. ## Open the results 1. In your project, open **Customers**, then **Surveys**, and select the **Surveys** tab. Select a survey in the list. 2. Select **Results** above the survey preview. On a narrow screen, the results open under the survey in the list. 3. Read the numbers at the top, then each question's answers below. 4. To take the answers elsewhere, select **Export CSV**. ![2 Results. 4 Export CSV.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106603504-01-results.png) ## What the numbers mean | **Number** | **What it counts** | | --- | --- | | **Shown** | How many times the survey was shown. | | **Completed** | How many people answered to the end. | | **Completion** | Of the people who answered at least one question, the share who finished. | | **NPS** | Promoters (9 to 10) minus detractors (0 to 6), as a percentage. It shows when the survey has an NPS question. Point at it to see how many answers it comes from. | | **CSAT** | The share of people who rated 4 or 5 out of 5. It shows when the survey has a Satisfaction question. | The bar in the survey list is different: it shows completed answers as a share of the times the survey was shown. Only finished responses count in the scores and in each question's answers. Unfinished ones count toward **Completion** and appear in the export. ## Each question's answers Each question shows how many people answered it, and for scales, the average. | **Question type** | **What you see** | | --- | --- | | **NPS** | The share of **Detractors**, **Passives** and **Promoters**, and how many people picked each score from 0 to 10. | | **Satisfaction**, **Effort** and **Rating** | How many people picked each score. | | **Pick one**, **Pick many** and **Yes / No** | How many people picked each option, most picked first. | | **Free text** and **Email** | The three newest answers. | To read more written answers, select **Show all** and the number of answers under the question. Rectify shows up to the 100 newest. The export has every one. ![The written answers to an NPS follow-up question.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106605138-02-written.png) ## Export the responses **Export CSV** shows once a survey has at least one finished response. The file has one row per person, newest first, including people who didn't finish. Its columns are **Response id**, **Visitor id**, **Started at**, **Completed at**, **Completed** (yes or no) and **Page**, then one column for each question. When someone picked several options, they're separated by semicolons. ## Troubleshooting ### It says "No answers yet" Nobody has finished the survey yet. Below it, Rectify tells you why: - "This survey is a draft. Publish it and answers appear here as visitors respond." Select **Publish** to put it live. - "Not shown to anyone yet." Check [who sees it and when](/rectify/help/a/103-choose-who-sees-a-survey-and-when). - "Shown 12 times, no completed answers yet." People saw it, with your own count, but nobody finished. ### There's no Export CSV button It shows once at least one person has finished the survey. ### Deleted a survey by mistake Deleting a survey also deletes its answers, and it can't be undone. Export the responses before you delete a survey you might need later. ## Read next - [Create a survey](/rectify/help/a/101-create-a-survey) - [Choose who sees a survey and when](/rectify/help/a/103-choose-who-sees-a-survey-and-when) --- # Create a monitor: HTTP, TCP port, Ping, DNS or Heartbeat Collection: Monitoring and Code Scan URL: https://app.rectify.so/rectify/help/a/89-create-a-monitor Watch a website, an API, a port, a DNS record or a scheduled job, and hear about it the moment it stops working. > **Note:** **Before you start.** Anyone on your team who can open the project can add monitors. How many monitors you can have, and how often they're checked, depends on your plan (see the table below). A monitor checks one thing on a schedule: a page or API, a port, a DNS record, a host, or a job that should check in with Rectify. When the checks fail, Rectify opens an incident and alerts the channels you pick. ## Add a monitor 1. Open **Monitoring**, then **Monitors**. 2. Select **Add monitor**. If you have no monitors yet, select **Let's GO!** instead. ![2 Add monitor, at the top of the Monitors page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106513089-01-add-monitor.png) 3. Under **Type**, pick what to check: **HTTP**, **TCP**, **DNS**, **Ping** or **Heartbeat**. You can't change the type later. 4. Enter the address to check. The table below shows what each type needs. 5. Enter a name. If you leave it empty, Rectify fills in the host name for you. 6. Add tags if you like, such as `prod` or `payments`. Press Enter or a comma after each one. You can use up to 10 tags. 7. Under **Check every**, choose how often Rectify checks it. ![3 Type. 4 The address. 5 Name. 7 Check every.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106514535-02-new-monitor.png) 8. Select **Create monitor**. The monitor shows up in the list straight away, and its first check runs within one interval. **Alert when** and **Notify** are optional here. [Add assertions and smart checks](/rectify/help/a/90-add-assertions-and-smart-checks) and [Set up alerting](/rectify/help/a/91-set-up-alerting) cover them. ## What each type checks | **Type** | **What it checks** | **What to enter** | | --- | --- | --- | | **HTTP** | The URL answers with an accepted status code (200 unless you change it) | A full URL that starts with `http://` or `https://` | | **TCP** | The host accepts a connection on a port | A host name or IP address, and the **Port** (1 to 65535) | | **DNS** | A record resolves | A domain, such as `example.com` | | **Ping** | The host answers ping (ICMP) | A host name or IP address | | **Heartbeat** | Your own job calls Rectify on time | Only a name. Rectify gives you the address to call | For more control, select **Show request options**: - **HTTP:** the **Method**, **Timeout (ms)** (1,000 to 60,000, 30,000 by default), **Follow redirects**, **Headers**, and a **Request body** for POST, PUT and PATCH. - **TCP:** the **Connection timeout (ms)**. - **DNS:** the **Record type** (A, AAAA, CNAME, MX, TXT or NS, A by default) and an **Expected value**. With an expected value, the check fails when no record contains it. - Every type: a **Description** of what the monitor watches and who owns it. ## Watch a scheduled job with Heartbeat A Heartbeat monitor works the other way round. Your job (a backup, an import, a cron task) calls a unique address when it finishes. If the call doesn't arrive on time, Rectify treats the job as failed. 1. Open **Monitoring**, then **Monitors**, and select **Add monitor**. 2. Under **Type**, select **Heartbeat**. 3. Name the job, for example "Weekly invoice export". 4. Under **Expect a ping every**, enter how often the job runs and pick **minutes**, **hours** or **days**. It can be anything from 1 minute to 30 days. 5. Set the **Grace period** in minutes. A ping that's late but inside the grace period counts as degraded, not down. ![2 Heartbeat. 3 Name. 4 Expect a ping every. 5 Grace period.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106516326-03-heartbeat.png) 6. Select **Create monitor**. 7. Open the new monitor and select the copy button next to its address to copy the ping URL. ![7 The copy button next to the ping URL.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106517957-04-ping-url.png) 8. Add a call to that URL at the end of your job, after the work has succeeded. ```bash curl -fsS https://api.rectify.so/v1/monitoring/heartbeat/YOUR_TOKEN ``` To report a run that failed, call the same URL with `/fail` on the end. Rectify records a failed check straight away instead of waiting for the grace period. ```bash curl -fsS https://api.rectify.so/v1/monitoring/heartbeat/YOUR_TOKEN/fail ``` Rectify re-checks Heartbeat monitors every minute, and the monitor goes down after the number of failed checks in a row you set (3 by default). Keep the ping URL private: anyone who has it can check in for your job. ## Monitors and check intervals on each plan | **Plan** | **Monitors** | **Fastest check** | | --- | --- | --- | | Idea (free) | 1 | Every 10 minutes | | Build | 3 | Every 5 minutes | | Launch | 10 | Every minute | | Accelerate | 25 | Every minute | | Enterprise | Unlimited | Every minute | Monitors count across your whole organization, not per project. Intervals faster than your plan allows show the plan they need in the **Check every** list. [Compare plans and what each one includes](/rectify/help/a/13-compare-plans) has the full list. > **Tip:** Moving from another uptime tool? Select **Import** on the Monitors page to bring in monitors from UptimeRobot, Better Stack, Pingdom or StatusCake, or paste a CSV or a list of URLs. ## Check it worked Open **Monitoring**, then **Monitors**. Your monitor shows **Up** once its first check passes, with its uptime and the time of the last check. Select it to see its checks, response times and incidents. ### It says "Monitors cannot target local or internal hostnames" Rectify only checks addresses on the public internet. Addresses such as `localhost`, internal host names and private or reserved IP ranges are blocked. Use the public address of the service. ### It says "DNS resolution failed - host not found" The host name doesn't exist yet, or it's misspelled. Check it opens from a browser or resolves with a DNS lookup tool, then try again. ### Create monitor is greyed out A required field is missing, such as the address, the name (at least 2 characters) or the TCP port. If the dialog says "You have reached the number of monitors your plan allows", every monitor on your plan is in use. Upgrade your plan, or ask an Owner or Admin to delete a monitor you no longer need. Pausing a monitor doesn't free its place. ### My Heartbeat monitor went down even though the job ran The job has to call the ping URL every time it finishes. Check the job reaches the internet, that the URL is copied in full, and that the interval under **Expect a ping every** matches how often the job really runs. Allow for slow runs with a longer **Grace period**. Next, choose what counts as down in [Add assertions and smart checks](/rectify/help/a/90-add-assertions-and-smart-checks), then send alerts to your team with [Set up alerting](/rectify/help/a/91-set-up-alerting). --- # Add assertions and smart checks Collection: Monitoring and Code Scan URL: https://app.rectify.so/rectify/help/a/90-add-assertions-and-smart-checks Decide what counts as down for a monitor, from status codes and slow responses to missing text, expiring certificates and your own assertions. > **Note:** **Before you start.** Anyone on your team who can open the project can change a monitor. SSL certificate and domain expiry checks need the Build plan or higher. Assertions work on HTTP monitors. ## Choose what counts as down 1. Open **Monitoring**, then **Monitors**, and select the monitor. 2. Open the menu (the three dots) on the monitor's card and select **Edit**. You can also set all of this when you create a monitor. 3. Under **Alert when**, set the rules you want. Rules with a switch only apply when the switch is on. ![3 The Alert when rules in the monitor's settings.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106520608-01-alert-when.png) 4. Select **Save changes**. The new rules apply from the next check. | **Rule** | **What it does** | | --- | --- | | **Status code is not accepted** | HTTP only. The status codes that count as up, separated by commas, such as `200, 204`. Any other code fails the check. It's 200 to start with. | | **Down after failed checks in a row** | How many checks must fail in a row before the monitor is down, from 1 to 10. It's 3 to start with. Fewer means faster alerts and more false alarms. | | **Response is slower than** | A time in milliseconds (100 or more). Checks that take longer count as a problem. | | **Body does not contain** | HTTP only. Text the page must include. The check fails when it's missing, which catches an error page that still answers 200. | | **SSL certificate expires within** | HTTPS addresses only. Rectify reads the certificate every day and warns your channels as the expiry date gets close. | | **Domain registration expires within** | Every type except Heartbeat. Rectify checks the domain's registration every day and warns when it's within the days you set (1 to 365), then again 7, 3 and 1 day before it lapses. | | **Uptime target** | A percentage from 90 to 100, 99.9 to start with. It sets the downtime allowance shown on the monitor page. | One failed check doesn't alert anyone. The monitor shows **Degraded** once about half the failed checks you set have happened in a row (2 of 3, for example), and **Down** when it reaches the full number. Down opens an incident and alerts your channels. ## Add assertions to an HTTP monitor Assertions test the response in more detail. Every assertion must pass, or the check fails. 1. Open the monitor's menu and select **Edit**. Under **Request**, select **Show request options**. 2. Under **Assertions**, select **Add assertion**. 3. Choose what to test: **Body**, **Header** or **Response time**. 4. Choose how to compare it (see the table below). 5. Enter the value to compare against. For a **Header**, enter the header name in the field below. For **JSON path**, enter the path there. ![2 Add assertion. 3 What to test. 4 How to compare. 5 The value.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106522629-02-assertions.png) 6. Select **Save changes**. | **Comparison** | **Passes when** | | --- | --- | | **Contains** | The value appears anywhere in the body or header | | **Does not contain** | The value doesn't appear | | **Equals** | The whole body or header is exactly the value | | **Does not equal** | The body or header is anything other than the value | | **Matches regex** | The body or header matches a regular expression | | **JSON path** | The value at a path in a JSON body equals the value you enter | For **Response time**, pick `lt` (less than), `lte` (less than or equal to), `gt` (greater than), `gte` (greater than or equal to) or `eq` (equal to), then enter a time in milliseconds. A few things to know: - A monitor can have up to 10 assertions, counting the **Body does not contain** rule. - Text comparisons ignore upper and lower case. - Type header names in lowercase, such as `content-type`. - Write JSON paths with dots and square brackets, starting from the top of the body, such as `data.status` or `items[0].id`. Leave out a leading `$.`. - Regular expressions can't use lookarounds or backreferences. ## Use the suggestions on the monitor page The monitor page lists **Suggestions** on the right. Each one is a quick fix for that monitor. **Enable** turns it on straight away, **Set up** opens the monitor's settings at the right place, and **Upgrade** shows the plans that include it. | **Suggestion** | **Shows when** | **What it does** | | --- | --- | --- | | **Watch the certificate** | An HTTPS monitor has no SSL check | Turns on SSL certificate expiry warnings | | **Watch domain expiry** | A monitor on a domain name has no domain check | Turns on domain registration warnings | | **Set a slow-response threshold** | **Response is slower than** is off | Opens **Alert when** | | **Check every minute** | The monitor checks less often than every minute | Switches to every minute, on Launch and higher | | **Add an escalation step** | The monitor has alert channels but no escalation | Opens **Notify** | ![The Suggestions on a monitor's page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106524264-03-suggestions.png) ## When a monitor keeps flipping If a monitor goes down and comes back up 4 times within 30 minutes, Rectify marks it **Flapping**. While it flaps, the down and recovered alerts are held back, so your team isn't flooded. Channels that have the **Flapping** event get one alert instead. The label clears once the monitor stays steady for 30 minutes. ## Check it worked The monitor's card lists its rules, such as "Down after 3 failed checks" and "Degraded over 2,000 ms". When a check fails, open the **Failed checks** tab on the monitor page: the **Detail** column shows why, for example which assertion failed. ### It says "This pattern is invalid or uses lookarounds or backreferences, which monitor checks do not support." Rewrite the regular expression without lookarounds (such as `(?=` or `(?!`) and backreferences (such as `\1`). A simpler pattern, or a **Contains** assertion, usually does the job. ### My header assertion always fails Check the header name is in lowercase, such as `content-type` rather than `Content-Type`, and that the header is really in the response. The **Failed checks** tab shows the reason for each failure. ### My JSON path assertion always fails Write the path without a leading `$.`, for example `data.status`. The body must be valid JSON, and the value at the path must equal what you entered. ### I can't turn on the SSL or domain checks They need the Build plan or higher. The switch shows the plan it needs. Select the plan label to see your options. Next, choose who hears about it in [Set up alerting](/rectify/help/a/91-set-up-alerting), and learn what to do when a monitor goes down in [Work an incident](/rectify/help/a/92-work-an-incident). --- # Set up alerting Collection: Monitoring and Code Scan URL: https://app.rectify.so/rectify/help/a/91-set-up-alerting Send monitor alerts to email, Slack, Discord, Teams, PagerDuty, a webhook, push, SMS or a phone call, and escalate when nobody answers. > **Note:** **Before you start.** Anyone on your team who can open the project can add and change alert channels. Only Owners and Admins can delete one. How many channels you can have depends on your plan, and phone call and SMS alerts need the Launch plan or higher (see the table below). Alerts go to **channels**. A channel is one destination, such as an email list or a Slack channel. You add it once under **Alerting**, then pick it on each monitor that should use it. ## Add an alert channel 1. Open **Monitoring**, then **Alerting**. 2. Select **Add channel**. If you have no channels yet, select **Let's GO!** instead. ![2 Add channel, at the top of the Alerting page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106527080-01-alerting.png) 3. Under **Type**, pick where alerts go. 4. Enter a **Name**, such as "Payments on-call". This is how you'll find it on a monitor. 5. Under **Destination**, fill in where to send it (see the table below). 6. Under **Events**, pick the alerts this channel should get. **All events** picks every one. ![3 Type. 4 Name. 5 Destination. 6 Events.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106528522-02-add-channel.png) 7. Select **Add channel**. | **Type** | **What you enter** | | --- | --- | | **Email** | Up to 10 **Recipients**. Press Enter or a comma after each address. | | **Slack** | The channel's incoming **Webhook URL**, and optionally a **Channel** and **Bot name** | | **Discord** | The channel's **Webhook URL**, and optionally a **Bot name** | | **Webhook** | Your endpoint's **URL**, the **Method** (POST or PUT), the **Authentication** (**None**, **Bearer token** or **Basic auth**) and an optional **Signing secret** | | **Phone call** | A **Phone number** with its country code. Quanta calls it and reads out the alert. | | **SMS** | A **Phone number** with its country code | | **Push** | The **Members** who get it in their Rectify app and browser. Each person's own notification settings still apply. | | **Teams** | The channel's **Incoming webhook URL** | | **PagerDuty** | The **Integration key** of an Events API v2 integration on your PagerDuty service. Recovered and resolved alerts resolve the same PagerDuty alert. | With a **Signing secret** set, every webhook delivery carries an `X-Rectify-Signature` header: an HMAC SHA-256 of the timestamp and body, so your endpoint can check it came from Rectify. Phone call and SMS alerts go through your own Twilio account. Connect Twilio under **Project settings**, **Integrations** first. ### The events you can pick | **Event** | **Sent when** | | --- | --- | | **Down** | A monitor fails enough checks in a row to go down | | **Recovered** | A monitor that was down passes its checks again | | **Degraded** | A monitor starts failing checks or answering slowly | | **Flapping** | A monitor keeps going down and up, so down and recovered alerts are held back | | **Incident opened** | An incident opens, by itself or reported by hand | | **Incident updated** | Someone posts an update on an incident | | **Incident resolved** | An incident is resolved | | **SSL expiring** | A monitored SSL certificate is close to expiring | | **Domain expiring** | A monitored domain's registration is close to lapsing | New channels start with **Down**, **Recovered**, **Incident opened** and **Incident resolved**. ## Pick channels for a monitor 1. Open the monitor, open its menu (the three dots) and select **Edit**. 2. Under **Notify**, open **Channels** and pick one or more. 3. To escalate, select **Add escalation step** and enter how many minutes to wait. 4. Open that step's **Channels** and pick who to alert next. ![2 Channels. 3 The wait in minutes. 4 The channels for that step.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106530519-04-notify.png) 5. Select **Save changes**. Escalation steps only run while nobody has acknowledged the incident. The first step fires its wait after the incident opens, and each later step fires its wait after the one before. A monitor can have up to 5 steps, each waiting 1 to 1,440 minutes. Acknowledging or resolving the incident stops the rest. A monitor with no channels still records its incidents, but nobody is alerted. ## Quiet hours and rate limits Both are at the bottom of a channel's settings. - **Quiet hours:** turn on **Silence this channel on a schedule**, then set **From**, **To**, the **Timezone** and the days. Nothing is sent to this channel inside that window. Incidents still open and show on your status page. - **Rate limit:** turn on **Cap alerts per window** and set the most alerts (1 to 100) per number of minutes (1 to 1,440). Alerts over the cap are dropped, not saved for later. ![Quiet hours and Rate limit in a channel's settings.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106532389-03-quiet-hours.png) While a monitor is in a maintenance window, its alerts are held back too. See [Plan maintenance windows](/rectify/help/a/93-plan-maintenance-windows). ## Test, turn off or remove a channel On the **Alerting** page, each channel has a switch to turn it on or off. Its menu (the three dots) has: - **Send test** sends a sample alert to that channel. - **Delivery log** lists every alert sent to it, with its event, monitor and whether it was **Sent** or **Failed**. - **Edit** and **Delete**. Deleting removes the channel from every monitor that uses it. Only Owners and Admins can delete. To test every channel on one monitor at once, open the monitor and select **Send test alert** in its **Notifications** panel. The test says that nothing is actually down. ## Alert channels on each plan | **Plan** | **Alert channels** | **Phone call and SMS** | | --- | --- | --- | | Idea (free) | 1 | No | | Build | 3 | No | | Launch | 5 | Yes | | Accelerate | 10 | Yes | | Enterprise | Unlimited | Yes | Channels count across your whole organization. ## Check it worked Select **Send test** on the channel and check the alert arrives. Then open the **Delivery log**: a test that went through shows **Sent**. The channel's row shows when it last sent an alert. ### The test says it failed Open the channel's **Delivery log** and read the **Detail** column. For Slack, Discord and Teams, check the webhook URL is still active in that app. For a webhook, check your endpoint accepts the request and answers with a success code. ### Phone call and SMS are greyed out or show a plan label They need the Launch plan or higher. If your plan includes them and the form says Twilio is not connected, connect Twilio under **Project settings**, **Integrations**, then come back. ### It says "You have reached the number of alert channels your plan allows" Every channel on your plan is in use. Upgrade, or ask an Owner or Admin to delete a channel you no longer need. ### Nobody got an alert when my monitor went down Check the monitor has channels under **Notify**, the channels are switched on, and **Down** is one of their events. Quiet hours, a rate limit or a maintenance window also hold alerts back. Next, learn what to do when an alert comes in with [Work an incident](/rectify/help/a/92-work-an-incident). --- # Work an incident Collection: Monitoring and Code Scan URL: https://app.rectify.so/rectify/help/a/92-work-an-incident Acknowledge an incident, post updates as you fix it, resolve it, or report one by hand. > **Note:** **Before you start.** Anyone on your team who can open the project can acknowledge, update, resolve and report incidents. Only Owners and Admins can delete one. An incident opens by itself when a monitor fails the number of checks in a row you set for it. It's named after the monitor, such as "Nightly database backup is down", and its first entry says what went wrong. It starts as **Minor** and becomes **Major**, then **Critical**, if the failures carry on. Rectify alerts the monitor's channels when it opens. ## Take an incident and keep everyone posted 1. Open **Monitoring**, then **Incidents**. The **Active** tab lists every open incident. 2. Select the incident to open it. ![2 An open incident in the Active tab.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106535201-01-incidents.png) 3. Select **Acknowledge** so your team knows someone is on it. This stops any escalation steps, and the timeline shows who acknowledged it. 4. Open the status menu at the bottom (it starts as **Keep Investigating**) and pick where things stand: **Investigating**, **Identified**, **Monitoring** or **Resolved**. 5. Write what's happening, in at least 10 characters. 6. Select the send button, or press Cmd+Enter (Ctrl+Enter on Windows). ![3 Acknowledge. 4 The status menu. 5 The update. 6 Send.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106536814-02-incident.png) Each update goes on the incident's timeline, to the monitor's alert channels, and on your status page with an email to its subscribers when the monitor is shown there. Write it for your customers. > **Tip:** Not sure what's wrong yet? Select **Quanta** (or **Explain**) next to the status menu. Quanta reads the monitor's check history and drafts an explanation. Select **Insert into update** to use it, then edit it before you send. Quanta uses your Rectify AI credits or your own AI provider key. ## Resolve an incident 1. In the status menu, pick **Resolved**. ![1 Resolved, in the status menu.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106538402-03-resolve.png) 2. Write what fixed it. 3. Select the send button. The incident moves to the **Resolved** tab with how long it lasted. You can also select **Resolve** from the menu on an incident's row. You don't always have to resolve it yourself. When the monitor passes 2 checks in a row, Rectify resolves the incident and adds "Monitor has recovered and is responding normally" to the timeline. ## Report an incident by hand Use this for problems your monitors can't see, such as a slow sign-in. 1. On the **Incidents** page, select **Report incident**. 2. Enter a **Title** of at least 5 characters. 3. Pick the **Monitor** it affects. 4. Choose the **Severity**: **Critical**, **Major** or **Minor**. 5. Under **What is happening**, describe it for your customers. This is optional. 6. Select **Report incident**. ![2 Title. 3 Monitor. 4 Severity. 5 What is happening. 6 Report incident.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106540020-04-report.png) The incident opens straight away, shows on your status page, and alerts the monitor's channels. ## Edit or delete an incident Open the incident, then open its menu (the three dots) at the top: - **Edit** changes the title and severity. The new ones show on the status page right away. - **Delete** removes the incident and its timeline from the status page and reports. It can't be undone, and only Owners and Admins can do it. ## Check it worked Your update appears at the top of the incident's timeline with your name and the new status. The incident's row on the **Incidents** page shows the same status, and the **Ack** column shows who acknowledged it. ### I resolved an incident and a new one opened The monitor was still failing. Resolving clears the count of failed checks, and once the monitor fails that many checks in a row again, a new incident opens. Fix the cause first, or wait for the monitor to recover on its own. To stop checks while you work, pause the monitor from its menu, or plan a maintenance window. ### The send button is greyed out Updates need at least 10 characters. ### Delete is greyed out Only Owners and Admins can delete incidents. Ask one of them, or resolve the incident instead. Next, choose who gets alerted and when in [Set up alerting](/rectify/help/a/91-set-up-alerting), and show incidents to your customers with [Publish a status page](/rectify/help/a/94-publish-a-status-page). --- # Plan maintenance windows Collection: Monitoring and Code Scan URL: https://app.rectify.so/rectify/help/a/93-plan-maintenance-windows Tell customers about planned work in advance, and pause checks and alerts while it happens. > **Note:** **Before you start.** Maintenance windows need the Build plan or higher. Anyone on your team who can open the project can schedule, edit and cancel one. Only Owners and Admins can delete one. A maintenance window covers planned work, such as a database upgrade. While it's in progress, Rectify skips the checks on the monitors it affects and holds back their alerts, so planned downtime doesn't open incidents or page anyone. Your status page shows the window before and while it runs. ## Schedule a window 1. Open **Monitoring**, then **Incidents**. 2. Select the **Maintenance** tab. 3. Select **Schedule maintenance**. ![2 The Maintenance tab. 3 Schedule maintenance.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106542642-01-schedule.png) 4. Enter a **Title** of at least 5 characters, such as "Database upgrade". 5. Under **Description**, tell customers what's happening and what to expect. 6. Pick when it **Starts** and **Ends**. The start must be in the future and the end after the start. 7. Under **Affected monitors**, open **Monitors** and pick at least one. 8. Leave **Notify subscribers** on to email your status page subscribers about it. ![4 Title. 5 Description. 6 Starts and Ends. 7 Affected monitors. 8 Notify subscribers.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106544085-02-dialog.png) 9. Select **Schedule**. You can also schedule a window for one monitor from its page: select **Schedule** in the **Maintenance** panel, and that monitor is already picked. ## What happens during the window - The window shows as **Scheduled**, then **In progress** at its start time, then **Completed** at its end. Rectify checks the times every 5 minutes, so a window can start or end a few minutes after the time you set. - While it's in progress, the affected monitors aren't checked and their alerts are held back. - With **Notify subscribers** on, your status page subscribers get an email when you schedule the window, when it starts and when it ends. - Your status page lists the window under **Maintenance** until it ends, if **Maintenance windows** is on in the status page settings. See [Publish a status page](/rectify/help/a/94-publish-a-status-page). ## Change or cancel a window On the **Maintenance** tab, open the window's menu (the three dots): - **Edit** changes the title, description, times, monitors or the notify setting. - **Cancel window** stops a scheduled or running window. Subscribers aren't emailed about the cancellation. - **Delete** removes it from the list and the status page. It can't be undone, and only Owners and Admins can do it. ![Edit, Cancel window and Delete, in a window's menu.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106545894-03-list.png) ## Check it worked The window appears on the **Maintenance** tab as **Scheduled**, with its affected monitors under its title, its start and end, and a tick under **Notify subscribers** if subscribers will be emailed. The tab's count shows how many windows are scheduled or in progress. ### It says "Start time must be in the future" Pick a start time later than now. To pause a monitor straight away instead, open it and select **Pause** from its menu. ### It says "Maintenance windows are not included in your plan" Maintenance windows start on the Build plan. Upgrade, or pause the monitors by hand while you work. ### My subscribers didn't get an email Subscribers are only emailed when **Notify subscribers** is on, **Status subscriptions** is on in the status page settings, and the window affects a monitor that's shown on the status page. Next, see how the window looks to your customers in [Publish a status page](/rectify/help/a/94-publish-a-status-page). --- # Publish a status page Collection: Monitoring and Code Scan URL: https://app.rectify.so/rectify/help/a/94-publish-a-status-page Show customers live uptime, incidents and planned maintenance on your portal, and let them subscribe to updates. > **Note:** **Before you start.** Owners, Admins and Members can change the portal. The status page is part of your portal and shows the monitors in this project, so add at least one monitor first. Your status page lives on your portal, next to your requests, roadmap and changelog. It shows whether your services are up, the incidents you're working on, past incidents and planned maintenance. ## Turn on the status page 1. Open **Publish**, then **Portal**. 2. Select the **Brand** tab on the right. 3. Under **Pages in the menu**, switch on **Status**. ![3 The Status switch under Pages in the menu.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106548316-01-pages.png) 4. In the bar above the preview, select **Status**. The first tab on the right now holds the status page settings. 5. Next to **Monitors shown**, open **Monitors** and pick the ones customers should see. Leave it empty to show every monitor. ![5 Monitors shown, in the status page settings.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106549770-02-settings.png) 6. Choose what else to show (see the table below). 7. Select **Save** at the bottom of the page. Keep the Status switch on: with it off, the page isn't listed in the portal menu and doesn't show any monitors. | **Setting** | **What it does** | | --- | --- | | **Monitors shown** | The monitors on the page, in the order you pick them. Empty shows every monitor. | | **Uptime percentages** | A daily uptime bar and an uptime figure next to every monitor | | **Uptime window** | How far back the uptime looks: **Last 7 days**, **Last 30 days** or **Last 90 days** | | **Response times** | The latest response time next to every monitor | | **Maintenance windows** | Shows planned maintenance before and while it runs | | **Status subscriptions** | Lets visitors sign up for emails about incidents and maintenance | Pick public-facing monitors, such as your website and API. Internal ones, like a backup job's heartbeat, are better left off. Paused monitors never show. ## What your customers see The page is at your portal's address with `/status` on the end. Select **Copy link** above the preview to copy it, or **View portal** at the top to open it. ![The status page as customers see it.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106551981-03-public.png) - **A summary at the top:** **All systems operational** when everything is up, or **Degraded performance**, **Partial outage** or **Major outage**, with the uptime over your window. - **Active incidents**, with every update you post on them. See [Work an incident](/rectify/help/a/92-work-an-incident). - **Each monitor**, with its uptime, its response time and its daily uptime bars. - **Past incidents**, newest first. - **Maintenance**, for windows that are scheduled or in progress. See [Plan maintenance windows](/rectify/help/a/93-plan-maintenance-windows). Only incidents on the monitors you show appear on the page, and everything you post in an incident's updates is public. Write updates for your customers. ## Let customers subscribe With **Status subscriptions** on, visitors select **Subscribe** on the status page and sign in with their email address. They then get an email when an incident opens, gets an update or is resolved, and about maintenance windows that have **Notify subscribers** on. Every email has a link to unsubscribe. ## Check it worked Open your portal in a private browser window. **Status** shows in the menu, and the page lists the monitors you picked with their current state. ### The page says "Nothing is being monitored yet" Check **Status** is switched on under **Pages in the menu** on the **Brand** tab and that you saved. The page also needs at least one active monitor in this project. Paused monitors aren't shown. ### An incident isn't on the status page Incidents only appear for the monitors you show. Add the monitor under **Monitors shown**, or leave the list empty to show every monitor. Next, keep customers posted during an outage with [Work an incident](/rectify/help/a/92-work-an-incident). --- # Scan your code with Code Scan Collection: Monitoring and Code Scan URL: https://app.rectify.so/rectify/help/a/95-scan-your-code-with-code-scan Connect GitHub, pick a repository and branch, and get a report on bugs, security vulnerabilities and code smells. > **Note:** **Before you start.** Code Scan needs the Build plan or higher and a GitHub repository. Anyone on your team who can open the project can connect GitHub and start a scan. Only Owners and Admins can delete a scan or disconnect GitHub. Code Scan reads the whole branch you pick and reports bugs, security vulnerabilities and code smells, each pointed at the file and line. ## Connect GitHub You only do this once per project. 1. Open **Monitoring**, then **CodeScan**. 2. Select **Connect GitHub**. ![2 Connect GitHub. The scans you have left this month are at the top.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106554624-01-connect.png) 3. GitHub opens. Install the Rectify app on your account or organization, choose the repositories it can see, and approve. GitHub sends you back to Code Scan, ready to run your first scan. ## Run a scan 1. On the Code Scan page, select **Let's GO!**. After your first scan, select **New Scan** at the top instead. 2. Under **Repository**, pick the repository. 3. Under **Branch**, pick the branch to scan. 4. Select **Start Scan**. The scan goes through four stages, **Queued**, **Fetch**, **Analyze** and **Process**, and the page shows its progress live. A scan usually takes a few minutes, longer for a large repository. You can leave the page and keep working. When it finishes, the page shows the results. [Read and act on Code Scan results](/rectify/help/a/96-read-and-act-on-code-scan-results) explains them. A few things to know: - A project runs one scan at a time. - Each scan replaces the previous results. Code Scan keeps the latest scan only. - The scan uses the branch as it is on GitHub, so push your changes first. ## Scans on each plan | **Plan** | **Scans a month** | | --- | --- | | Idea (free) | None | | Build | 10 | | Launch | 25 | | Accelerate | 100 | | Enterprise | Unlimited | Scans count across your whole organization, and the count resets on the 1st of each month. A scan counts when it starts, even if it fails. The badge at the top of the Code Scan page shows how many you have left, such as "8/10 scans left". ## Check it worked After you select **Start Scan**, you see "Scan started successfully!", and the page shows **Scanning your repository** with the repository and branch. When it's done, the page shows **Quality gate passed** or **Quality gate failed** and the issue list. ### It says "Reconnect required" or "Couldn't load your repositories" Rectify can no longer reach your repositories on GitHub, often because the app's access was changed or removed. Select **Re-authenticate** and approve the Rectify app on GitHub again. Check it can see the repository you want to scan. ### It says "You've reached the maximum number of code scan quotas per month" Your organization has used every scan on its plan this month. Wait for the count to reset on the 1st, or upgrade your plan. On the free Idea plan, Code Scan isn't included. ### It says "A scan is already in progress for this project" Each project runs one scan at a time. Wait for the current scan to finish, then start the next one. ### The scan failed The page shows **Scan failed** with the reason. Check the repository and branch still exist on GitHub and that Rectify can still see them, then start a new scan. Next, see what the report means and what to fix first in [Read and act on Code Scan results](/rectify/help/a/96-read-and-act-on-code-scan-results). --- # Read and act on Code Scan results Collection: Monitoring and Code Scan URL: https://app.rectify.so/rectify/help/a/96-read-and-act-on-code-scan-results Understand the quality gate and issue counts, filter the issue list, and use each issue's details to fix it. > **Note:** **Before you start.** Anyone on your team who can open the project can read scan results. You need a finished scan first: see [Scan your code with Code Scan](/rectify/help/a/95-scan-your-code-with-code-scan). Open **Monitoring**, then **CodeScan**. The page shows the results of the latest scan. ## The summary The bar at the top shows the result and which repository and branch were scanned, who started the scan and when. - **Quality gate passed** means the code met the quality bar. **Quality gate failed** means it didn't. - The counts below show the open issues by type: | **Count** | **What it covers** | | --- | --- | | **Bugs** | Coding errors that can lead to wrong behavior or crashes | | **Vulnerabilities** | Security weaknesses an attacker could use | | **Code Smells** | Code that works but is harder to understand, change or extend | ## Find the issues that matter The issue list sits under the summary. Each issue shows its message, its type, its severity, and the file and line it's on. - Open **Severity** to show only **Blocker**, **Critical**, **Major**, **Minor** or **Info** issues. - Open **Type** to show only **Bug**, **Vulnerability** or **Code Smell** issues. - Select **Reset** to clear the filters. More issues load as you scroll. Work from the top severities down: blockers and critical vulnerabilities first. ## Read an issue Select an issue to see its details. On a narrow screen, they open from the bottom. | **Tab** | **What it shows** | | --- | --- | | **Issue** | **What is the Issue?**, **Why is this an Issue?**, and the **File**, **Line** and **Effort** (roughly how long the fix takes), with its tags | | **Resolution** | **How to Resolve This Issue**: what to change to fix it | | **Code** | The lines around the issue, with the issue's line highlighted | ## Fix and check again 1. Fix the issue in your code and push it to the branch. 2. Select **New Scan** at the top of the Code Scan page. 3. Pick the same repository and branch, and select **Start Scan**. When the new scan finishes, fixed issues drop off the list and the counts go down. The new scan replaces the old results, so note anything you still need before you start it. > **Tip:** Ask Quanta "How did the last code scan go?" to see the result, the counts and the top issues in a panel. From there, **Run new scan** shows the repository and branch and starts a scan once you confirm, and **Open Code Scan** opens the full report. ## Get told when a scan finishes Rectify can send you a push notification when a scan finishes, fails or finds issues. Select your name at the bottom of the sidebar, then **Notifications**, and use the switches under **Code Analysis**. ![Scan Completed, Scan Failed and Issues Detected under Code Analysis.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106557435-01-notifications.png) ## Delete a scan Owners and Admins can remove the latest scan and its results with the bin icon on the summary bar. Select **Delete** to confirm. It can't be undone. ### The issue list is empty If the scan finished and the summary shows no bugs, vulnerabilities or code smells, there's nothing to fix: the list says "No issues found". If you've set a **Severity** or **Type** filter, select **Reset**. ### The page shows "Ready to run a code scan" although I ran one The latest scan was deleted, or the page lost its live connection. Reload the page. If there's still no scan, run a new one. --- # Build your first workflow Collection: Workflows and automation URL: https://app.rectify.so/rectify/help/a/73-build-your-first-workflow Connect a trigger to the steps that should follow it, so routine work in your project happens on its own. > **Note:** **Before you start.** Owners, Admins and Members can create and change workflows, on every plan. Only Owners and Admins can delete one. A workflow starts with one **trigger**, the event that sets it off, and runs the **actions** connected below it. This example sends every new bug report to one teammate and leaves a note for the team. ## Build the workflow 1. Open **Project settings**, then **Workflows**. 2. Select **New workflow**. If it's your project's first workflow, select **Let's GO!** instead. ![2 New workflow, above the list of workflows.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106435319-01-new-workflow.png) 3. Under **Nodes**, open **Triggers**, then **Feedback**. Drag **Feedback Created** onto the canvas. 4. Select the new node. In the panel on the right, set **Feedback Type** to **Bug**, so only bug reports start the workflow. ![3 Feedback Created in the list of nodes. 4 Feedback Type, set to Bug.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106436909-02-trigger.png) 5. Open **Actions**, then **Feedback**, and drag **Assign Feedback** onto the canvas below the trigger. 6. Connect them: drag from the dot under **Feedback Created** to the dot on top of **Assign Feedback**. 7. Select **Assign Feedback** and pick a teammate under **Assign To**. Leave **Feedback** empty, so the step works on the report that started the workflow. 8. Add **Add Feedback Note** the same way and connect it below **Assign Feedback**. Write the **Note Message**, and select **Variables** to insert details from the report, such as its title. ![6 The connection between two nodes. 8 Variables, beside the Note Message.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106438745-03-connected.png) 9. Select **Save Workflow**, enter a **Workflow name** of up to 80 characters, and select **Create**. ![9 Create, under the Workflow name.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106440380-04-create.png) Your workflow is switched on as soon as you create it. From now on, every new bug report in this project is assigned and gets the note. ## Tips for the canvas - Steps run one after another, from the trigger down. A step can use what the steps above it produced. - Select **Format** at the top of the canvas to line the nodes up neatly. - To remove a node, select it and select **Delete Node** at the bottom of the panel. - To change what a node is called on the canvas, edit its **Label**. ## Change it later Select the workflow's name in the list to open it. While every node is connected, changes save on their own a few seconds after you make them, and the top of the page shows **All changes saved**. To stop the workflow for a while, turn off the switch next to **Active** at the top. It then shows as **Paused** in the list. ## Check it worked The workflow appears in the list on the **Workflows** page with the status **Active** and its trigger. After it runs, **Last 12 runs**, **Runs** and **Last run** fill in. [Test a workflow and read its runs](/rectify/help/a/77-test-a-workflow-and-read-its-runs) shows how to try it on a real report first. ### It says "Only one trigger node is allowed per workflow" A workflow has exactly one trigger. Delete the extra trigger, or build a second workflow for the other event. ### It says "All nodes must be connected to the trigger" A node on the canvas isn't linked to anything above it. Connect it, or select it and select **Delete Node**. ### It says "A workflow with the same trigger and configuration already exists in this project" Another workflow in this project already uses the same trigger with the same settings. Add your steps to that workflow, or change the trigger's settings, for example the **Feedback Type**. Next, see every [workflow trigger](/rectify/help/a/74-workflow-triggers) and [workflow action](/rectify/help/a/75-workflow-actions) you can use. --- # Workflow triggers: what can start a workflow Collection: Workflows and automation URL: https://app.rectify.so/rectify/help/a/74-workflow-triggers Every event that can start a workflow, and the settings that narrow down when it runs. > **Note:** **Before you start.** Owners, Admins and Members can add and change triggers, on every plan. The trigger is the first node of a workflow: the event it waits for. In the workflow builder, open **Triggers** under **Nodes** to see them in groups, then drag one onto the canvas. ![The trigger groups under Nodes.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106442975-01-groups.png) Select the trigger on the canvas to see its settings on the right. Most triggers can be narrowed down, for example to one board or one type of feedback. Leave a setting on **Any** to run for all of them. ![A trigger's settings: Board and Vote Threshold for Post Reaches Votes.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106444458-02-settings.png) ## Feedback | **Trigger** | **Runs when** | **Settings** | | --- | --- | --- | | **Feedback Created** | Someone sends feedback. | **Feedback Type**: **Bug**, **Idea**, **General** or **Testimonial** | | **Feedback Status Changed** | A report's status changes. | **From Status** and **To Status**: **Open**, **In Progress**, **Under Review** or **Resolved** | | **Feedback Resolved** | A report is marked **Resolved**. | **Feedback Type** | | **Feedback Assigned** | A report is assigned to a teammate. | None | | **Help Article Rated** | A reader answers "Was this helpful?" on a help article. | **Rating**: **Helpful only** or **Not helpful only** | Changes that a workflow makes itself, such as **Update Feedback Status**, don't start these triggers. That keeps one workflow from setting off another in a loop. ## Portal | **Trigger** | **Runs when** | **Settings** | | --- | --- | --- | | **Post Created** | A new post is added to a board. | **Board** | | **Post Status Changed** | A post moves from one status to another. | **Board**, **From Status**, **To Status** | | **Post Reaches Votes** | A post reaches the number of votes you set. | **Board**, **Vote Threshold** | | **Post Commented** | Someone comments on a post. | **Board**, **Comment Author**: **Anyone**, **Portal visitors** or **Your team** | | **Post Waiting for Review** | A submitted post is held for review. | **Board** | | **Post Approved** | A held post is approved. | **Board** | | **Post Declined** | A held post is declined. | **Board** | | **Post Merged** | A post is merged into another as a duplicate. | **Board** | | **Post Tagged** | A tag is added to a post. | **Board**, **Tag** | **Post Status Changed** needs a board. The two status lists open once you pick one. **Post Reaches Votes** runs once per post, on the vote that reaches your number. Set **Vote Threshold** to 0 to run on every vote. If your workflow comments on posts, keep **Post Commented** on **Portal visitors**. Your workflow's own comment then won't start it again. ## Changelog | **Trigger** | **Runs when** | | --- | --- | | **Changelog Published** | A changelog entry goes live, including a scheduled entry when its time comes. | | **Changelog Subscriber Added** | Someone subscribes to your changelog. | ## Inbox | **Trigger** | **Runs when** | | --- | --- | | **Inbox Message Received** | A new message arrives in a support conversation with your team. Your team's replies count too. | | **Inbox Mentioned** | A teammate is mentioned in a support conversation. | Keep **Inbox Type** on **Any** for both. ## Code Scan, Monitoring and Contacts | **Trigger** | **Runs when** | **Settings** | | --- | --- | --- | | **Code Scan Issue Detected** | A finished code scan finds bugs or vulnerabilities. | Keep **Severity** and **Issue Type** on **Any** | | **Monitor Down** | A monitor goes down. | **Monitor**: **Any monitor** or one monitor | | **Monitor Up** | A monitor recovers. | **Monitor** | | **Incident Created** | A new incident is opened. | **Severity**: **Low**, **Medium**, **High** or **Critical** | | **Incident Resolved** | An incident is resolved. | **Severity** | | **Contact Enters a Segment** | A contact starts matching a segment. | **Segment**: **Any segment** or one segment | | **Contact Leaves a Segment** | A contact stops matching a segment. | **Segment** | ## Rules for every trigger - A workflow has one trigger. To react to two events, build two workflows. - Each project can have one workflow per trigger and settings. A second **Feedback Created** workflow for bugs is refused, but one for ideas is fine. - Only workflows that are switched on run. A paused workflow ignores its trigger. - Every step after the trigger can use the trigger's details, such as the report's title. [Add AI steps and use data from earlier steps](/rectify/help/a/76-add-ai-steps-and-variables) shows how. Next, see what a workflow can do in [Workflow actions](/rectify/help/a/75-workflow-actions). --- # Workflow actions: what a workflow can do Collection: Workflows and automation URL: https://app.rectify.so/rectify/help/a/75-workflow-actions Every step a workflow can take, from assigning feedback to posting in Slack, and what each one needs. > **Note:** **Before you start.** Owners, Admins and Members can add and change actions, on every plan. Actions that use another service, such as Slack, Jira or Twilio, need that service connected to the project under **Project settings**, **Integrations**. Actions are the steps that run after the trigger. In the workflow builder, open **Actions** under **Nodes**, drag one onto the canvas and connect it below the trigger or another step. Select it to fill in its settings on the right. ![The action groups under Nodes.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106447098-01-groups.png) ## Feedback | **Action** | **What it does** | **Settings** | | --- | --- | --- | | **Update Feedback Status** | Changes a report's status. | **Feedback**, **New Status** | | **Assign Feedback** | Assigns a report to a teammate. | **Feedback**, **Assign To** | | **Add Feedback Note** | Adds a note your team sees on the report. | **Feedback**, **Note Message** | | **Move Feedback** | Moves a report to another project in your organization. | **Feedback**, **Move To Project** | When the trigger is a feedback trigger, such as **Feedback Created**, leave **Feedback** empty. The step then works on the report that started the workflow. With any other trigger, pick a report. ## Portal | **Action** | **What it does** | **Settings** | | --- | --- | --- | | **Create Post** | Adds a post to a board. | **Board**, **Status**, **Title**, **Description** | | **Change Post Status** | Moves a post to another status. | **Board**, **To Status** | | **Comment on Post** | Adds a comment to a post. | **Post**, **Comment**, **Internal note** | | **Tag Post** | Adds a tag to a post. | **Post**, **Tag** | | **Move Post to Board** | Moves a post to another board. | **Post**, **Board** | | **Approve Post** | Approves a post waiting for review. | **Post**, **Status** | | **Decline Post** | Declines a post waiting for review. | **Post** | | **Merge Post** | Merges a duplicate into another post. | **Duplicate Post**, **Keep This Post** | For **Post**, keep **The post from the trigger** to act on the post that started the workflow, or pick a post. Turn on **Internal note** to keep a comment for your team only. When you merge, votes and followers move onto the post you keep. ## Changelog | **Action** | **What it does** | **Settings** | | --- | --- | --- | | **Create Changelog Entry** | Creates a draft changelog entry. | **Title Template**, **Content Template**, **Image** | | **Publish Changelog** | Publishes a draft entry straight away. | **Changelog Entry** | | **Link Post to Changelog** | Links a post to a changelog entry. | **Post**, **Changelog Entry** | **Create Changelog Entry** needs a cover image: upload one, or select **Nano Banana** to use an image an AI step made. **Publish Changelog** can publish **The entry an earlier step created**, and it sends the update email if the entry has notifications on. Everyone following a linked post hears about the entry. ## Notifications | **Action** | **What it does** | **Settings** | | --- | --- | --- | | **Send Email** | Sends an email. | **To**, **Subject**, **Body** | | **Send Push Notification** | Sends a push notification to your team. | **Title**, **Body**, **URL** | | **Make Phone Call** | Quanta calls a phone number and talks through your message. Needs Twilio. | **Phone Number**, **Message (Optional)** | | **Send SMS** | Sends a text message. Needs Twilio. | **Phone Number**, **Message** | ![The Send Email settings.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106448706-02-send-email.png) When **Send Email** goes to one of your project's contacts, Rectify respects their email preferences, so someone who unsubscribed doesn't get it. ## Code Scan and Monitoring | **Action** | **What it does** | | --- | --- | | **Trigger Code Scan** | Starts a code scan of a repository. Needs GitHub connected. | | **Create Incident** | Opens an incident on a monitor, with a **Title**, **Message** and **Severity**. | | **Resolve Incident** | Resolves an incident, with a closing **Message**. | | **Pause Monitor** | Pauses a monitor. | | **Resume Monitor** | Resumes a paused monitor. | ## Integrations | **Action** | **What it does** | | --- | --- | | **Send to Slack** | Posts your **Message Template** to the Slack channel connected to the project. | | **Send Webhook** | Sends a request to a **Webhook URL**, with the **Method**, **Headers (JSON)** and **Body (JSON)** you set. | | **Create GitHub Issue** | Creates an issue in the connected GitHub repository. | | **Create Jira Issue** | Creates an issue in Jira. | | **Create Linear Issue** | Creates an issue in Linear. | | **Create GitLab Issue** | Creates an issue in GitLab. | | **Create Trello Card** | Creates a card in Trello. | | **Create Asana Task** | Creates a task in Asana. | | **Create Monday Item** | Creates an item in Monday.com. | If a service isn't connected, its settings say so and offer a button to connect it. ## Fill in text with details from the run Text settings with a **Variables** button, such as **Subject**, **Body** or **Note Message**, can include details from the trigger or from earlier steps. Select **Variables** and pick one, and it's added where your cursor is, for example `{{trigger.feedback.title}}`. [Add AI steps and use data from earlier steps](/rectify/help/a/76-add-ai-steps-and-variables) explains how this works. ### A step failed with "Slack integration not enabled for this project" Slack isn't connected to this project. Connect it under **Project settings**, **Integrations**, then run the workflow again. ### It says a Feedback node "requires a feedback ID" The workflow's trigger isn't a feedback trigger, so the step has no report to work on. Pick a report under **Feedback**, or use a feedback trigger. Next, [add AI steps](/rectify/help/a/76-add-ai-steps-and-variables), or [test a workflow and read its runs](/rectify/help/a/77-test-a-workflow-and-read-its-runs). --- # Add AI steps and use data from earlier steps Collection: Workflows and automation URL: https://app.rectify.so/rectify/help/a/76-add-ai-steps-and-variables Let AI write or summarize as part of a workflow, and pass details from the trigger and earlier steps into later ones. > **Note:** **Before you start.** Owners, Admins and Members can change workflows. AI steps run on your plan's AI credits, or on the AI provider you connected under **Organization settings**, **AI providers** when you have no credits. [Compare plans](/rectify/help/a/13-compare-plans) lists the credits on each plan. ## Add an AI step 1. Open the workflow, then open **AI** under **Nodes**. 2. Drag **AI Summarize** or **AI Generate Text** onto the canvas and connect it below the trigger. 3. Select it and pick an **AI Model**. **Best** picks the best model available to you. 4. For **AI Summarize**, write what the summary should focus on in **Input Text**. For **AI Generate Text**, write the **Prompt**. ![3 AI Model. 4 Input Text. Output Variable shows the name the result is saved under.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106451793-01-ai-step.png) The result is saved under the name in **Output Variable**, ready for the steps below it. | **AI step** | **What it does** | **Output Variable** | | --- | --- | --- | | **AI Summarize** | Summarizes the trigger's details and what earlier steps produced, following your **Input Text**. When a new feedback report comes with screenshots, an attachment or a session replay, it can look at those too. | `summary` | | **AI Generate Text** | Writes text from your **Prompt**, such as a changelog draft or a reply. The trigger's details are added to the prompt for you. | `generatedText` | | **Nano Banana** | Makes an image from your **Prompt**, with an optional **Reference Image (Optional)** to guide it. Pick **Nano Banana** for 1024 px images, or **Nano Banana Pro Preview** for up to 4K. | `generatedImageUrl` | **Nano Banana** is listed only when a Gemini key is connected under **Organization settings**, **AI providers**. Its image can be the cover of a **Create Changelog Entry** step. **AI Summarize** and **AI Generate Text** write plain text, without Markdown symbols. ## Use the result in a later step 1. Connect a step below the AI step, for example **Add Feedback Note**, and select it. 2. Select **Variables** beside a text setting, such as **Note Message**. 3. Under **Previous Nodes**, pick the AI step's result, for example **AI Summarize: Summary**. It's added where your cursor is. ![2 Variables. 3 AI Summarize: Summary, under Previous Nodes.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106453630-02-variables.png) ## How variables work A variable is a placeholder in double curly brackets. When the workflow runs, Rectify swaps it for the real value. - Under **Trigger**, you find the details of the event that started the run, such as **Feedback Title** (`{{trigger.feedback.title}}`) or **Feedback Priority**. - Under **Previous Nodes**, you find what the steps above this one produced. A step only sees the steps connected above it. - You can type a variable yourself, or mix several into one sentence: `New bug: {{trigger.feedback.title}} ({{trigger.feedback.priority}} priority)`. - If a value is missing when the workflow runs, the placeholder stays in the text as you wrote it. To run steps only for some events, use the trigger's settings, such as **Feedback Type**, or build a separate workflow for each case. ## Check it worked Run the workflow on a real report and open the run's details. Each step shows its **Output**, including the AI step's text. [Test a workflow and read its runs](/rectify/help/a/77-test-a-workflow-and-read-its-runs) shows how. ### An AI step failed with "AI settings not configured for this organization" Your organization has no AI credits left and no AI provider connected. Connect one under **Organization settings**, **AI providers**. ### I don't see Nano Banana It's listed only when a Gemini key is connected under **Organization settings**, **AI providers**. --- # Test a workflow and read its runs Collection: Workflows and automation URL: https://app.rectify.so/rectify/help/a/77-test-a-workflow-and-read-its-runs Run a workflow on a real report, post or monitor, then check what each step did and why a run failed. > **Note:** **Before you start.** Everyone who can open the project can start a test run, read run history and switch a workflow on or off. > **Warning:** A test run does everything for real. It changes reports and posts, and it sends any emails, Slack messages, webhooks or texts in the workflow. Test on something safe, or point those steps at your own team first. ## Run a test 1. Open **Project settings**, then **Workflows**, and select the workflow. 2. Make sure the switch at the top reads **Active**. You can only test a workflow that's switched on, and while it's on it also runs on real events. 3. Select **Test Run**. ![2 The Active switch. 3 Test Run, beside View Runs.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106456243-01-toolbar.png) 4. Pick the item to run it on. The list matches the trigger: feedback for a feedback trigger, posts for a post trigger, monitors, incidents, chats or subscribers for the others. 5. Select **Run Workflow**. ![4 A feedback report picked as trigger data. 5 Run Workflow.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106457681-02-pick.png) Rectify shows **Workflow triggered successfully** and runs the steps in the background. A test run skips the trigger's settings: a workflow set to **Bug** still runs on an idea you pick. You can also start a test from the list: open the menu at the end of the workflow's row and select **Test run**. ## Read the runs Select **View Runs** at the top of the workflow, or **View runs** in its menu on the list. Each run shows: | **Column** | **What it tells you** | | --- | --- | | **Status** | **Completed**, **Failed**, **Running** or **Pending** | | **Triggered By** | **Event** when the trigger started it, **Manual** for a test run | | **Started At** | When it began | | **Duration** | How long it took | | **Nodes** | How many steps ran, how many finished and how many failed | ![The Workflow Runs page, with the button that opens a run's details.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106459299-03-runs.png) Select the eye button at the end of a row to open **Workflow Run Details**. Under **Node Execution**, each step shows whether it finished, any error, and its **Output**: the data it received or produced, such as the report from the trigger or the text an AI step wrote. ![Workflow Run Details, with each step and its output.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106460742-04-details.png) ## When a run fails Steps run one at a time, from the trigger down. If a step fails, the run stops there and the steps below it don't run. The run shows **Failed** with the error, and the failed step shows it too. On the **Workflows** page, the workflow moves to the **Failing** tab, with the error under its status. Your team gets a push notification, and Quanta posts the failure in its Project Report chat. Once a run succeeds again, the workflow is back to **Active**. ## Check it worked Open the item you ran the test on. For the example in [Build your first workflow](/rectify/help/a/73-build-your-first-workflow), the report now has its assignee and the new note. ### It says "Cannot run inactive workflow" The workflow is switched off. Turn on the switch at the top so it reads **Active**, then run the test again. ### The list says "No feedbacks available" There's nothing to run the workflow on yet. Wait for the first report, post or event of that kind, or send a test report from your own site. ### It says "Board selection required" Pick a specific board in the trigger's settings, then try the test again. --- # Use the Automation page Collection: Workflows and automation URL: https://app.rectify.so/rectify/help/a/78-use-the-automation-page Score your leads, post contact activity to Slack and send events to your own systems with signed webhooks. > **Note:** **Before you start.** Owners, Admins and Members can set up lead scoring, Slack alerts and webhooks, on every plan. Only Owners and Admins can delete an alert or a webhook endpoint. Slack alerts need Slack connected to the project under **Project settings**, **Integrations**. Open **Project settings**, then **Automation**. The page has three tabs: **Lead scoring**, **Slack alerts** and **Webhooks**. ![The three tabs, and Let's GO! to add the first scoring rule.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106463302-01-tabs.png) ## Score your leads Lead scoring gives each contact a number from the things they are and do, so the people closest to buying rise to the top of your contacts. 1. Open the **Lead scoring** tab. 2. Select **Let's GO!**. Later rules start from **Add rule**. 3. Under **What kind of signal is this**, pick **Who they are** for a fact about the contact, such as their plan or company size, or **What they did** for something they did within a number of days. 4. Enter a name under **Name it**, then set the condition under **When this is true** or **When this happens**. For **What they did**, turn on **Score every time** to give points each time it happens, up to a cap. 5. Set what it's **Worth** in points, then select **Add rule**. Use a negative number for a signal pointing the wrong way, like a refund. ![3 What kind of signal is this. 5 Worth. Fill an example fills the rule with a sample.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106464920-02-rule.png) 6. Turn on the switch next to **Lead scoring** to start calculating, then select **Save** at the bottom. Rectify recalculates every score after you save. A project can have up to 50 rules. - **Bands** name ranges of scores. Contacts take the highest band their score reaches. New projects start with cold from 0, warm from 40 and hot from 80, and you can have up to 10. - **Decay half-life** halves a contact's score for every that many days they stay quiet. Leave it at 0 to keep scores forever. - Every contact shows its score and band in your contacts and on their profile, and segments can filter on them. If HubSpot is connected, the button at the top pushes scores there. ## Send Slack alerts Slack alerts post to the Slack channel connected to the project when something happens to your contacts or feedback. If Slack isn't connected, the tab shows **Slack is not connected** with a **Connect** button. 1. Open the **Slack alerts** tab and select **Let's GO!**, or **New Alert** at the top once you have one. 2. Enter a **Name**, such as Critical bugs to #engineering. 3. Under **When this happens**, tick the events that should post. Any one of them sends the alert. 4. Narrow it down if you like: **Only for this segment**, **Minimum score** or **Only for this band**. These appear only when every event you picked carries a contact or a segment. 5. Set a **Cooldown (min)**, up to 1,440 minutes, so one busy contact can't flood the channel. 6. Select **Create alert**. Each alert has a switch to pause it, and buttons to edit or delete it. ## Send events with webhooks A webhook sends each event to a web address you own, such as your CRM. Every request is signed, so your server can check it came from Rectify. 1. Open the **Webhooks** tab and select **Let's GO!**, or **Add Endpoint** at the top once you have one. 2. Enter the **URL**. It must be a public HTTPS address. 3. Add a **Description**, then tick the **Events** to send. Leave them all unticked to receive every event, including ones added later. 4. Select **Create endpoint**. ![2 URL. 3 An event ticked under Events.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106466757-03-webhook.png) 5. Copy the secret in **Save your signing secret**. It's shown only once, and your server uses it to check the **X-Rectify-Signature** header. The events cover new feedback, status changes and assignments, contacts, segments, lead score bands, forms, surveys and the help center. Each endpoint shows its recent deliveries. Its buttons send a test event, rotate the signing secret, pause it or delete it. Rectify tries a failed delivery up to 5 times. If an endpoint keeps failing, Rectify pauses it and marks it **Paused**. Fix your server, then switch it back on. ## Check it worked - **Lead scoring:** the line under **Lead scoring** reads **Scoring is on**, with the points available from your active rules. - **Slack alerts:** the alert appears in the list, switched on. - **Webhooks:** select the test button on the endpoint and look for the delivery in its recent deliveries. ### The delete button is greyed out Only Owners and Admins can delete Slack alerts and webhook endpoints. Pause it with its switch instead, or ask an Owner or Admin to delete it. ### It says "No contact fields yet, so there is nothing to score on" Rectify hasn't seen any contacts in this project yet. Install the Rectify script and identify your users first. ### The URL is rejected Webhooks only go to public HTTPS addresses. Private and internal addresses, such as localhost, are refused. To run steps of your own when something happens, [build a workflow](/rectify/help/a/73-build-your-first-workflow) instead. --- # Customize your project's email notifications Collection: Workflows and automation URL: https://app.rectify.so/rectify/help/a/79-customize-project-email-notifications Change the wording, logo and colour of the emails Rectify sends for your project, or switch an email off. > **Note:** **Before you start.** Everyone who can open the project can edit these emails, on every plan. Hiding **Powered by Rectify** needs the Launch plan or above. Rectify sends a few emails on your project's behalf, for example a thank-you when someone sends feedback. Open **Project settings**, then **Email notifications**, to change what they say and how they look. ## The emails Rectify sends | **Template** | **Who gets it** | **Variables** | | --- | --- | --- | | **Feedback Received** | The person who sent feedback, when they left an email address. | `{{reporter_name}}` | | **Chat Request** | The person a teammate invites to a chat, for example from a feedback report. | `{{recipient_name}}`, `{{chat_link}}`, `{{title}}` | | **New Inbox Message** | A visitor who is away when a teammate replies in their chat. It also tells your team about a new visitor message when the teammate handling the chat is away. | `{{recipient_name}}`, `{{chat_link}}`, `{{title}}` | | **Feature Request Status Update** | Nobody. It shows **Not sent**: the status update email people get has fixed text. | `{{reporter_name}}`, `{{status}}` | Teammates who don't want these can turn off **Support Inbox Message** in their notification settings. ## Edit a template 1. Open **Templates**. 2. Select the template, for example **Feedback Received**. The preview on the right shows it the way people get it. ![2 Feedback Received, with its preview.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106469522-01-templates.png) 3. Select **Editor** above the preview. 4. Change the **Subject** and the **Message**. Select a variable under **Insert variable** to add it at the end of the message. ![3 Editor. 4 Subject, with the variable you can insert below it.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106471168-02-editor.png) 5. Select **Save** in the bar at the bottom. **Discard** throws your changes away. When the email goes out, each variable is replaced: `{{reporter_name}}` and `{{recipient_name}}` with the person's name, `{{chat_link}}` with a link to the chat, and `{{title}}` with the title from **General**. To stop an email, select the pause button on its row, or turn off **Send Email** in the editor, and save. The row then shows **Off** instead of **On**. ## Write a template with AI 1. Open **Write with AI**. 2. Describe what to change, for example "Make the chat invite friendlier and shorter", or pick one of the suggestions. To start from a ready-made draft, pick an example such as **Set expectations** under **Or start from an example**. 3. Quanta replies with a draft for one template. Ask for changes until you like it, then select **Open in editor**. ![3 Open in editor, under the draft.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106473078-04-write-with-ai.png) 4. Check the draft in the editor and select **Save**. The chat isn't saved. If you leave or refresh the page before saving, the draft is gone. ## Logo, colour and sender Open **General** to set what every email looks like. ![The General and Sending domain settings.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106474752-03-general.png) | **Setting** | **What it does** | | --- | --- | | **Logo** | Shown above the title. JPG, PNG or GIF, up to 4 MB. | | **Title** | Shown under the logo. It's also the sender name when you send from your own domain. | | **Brand Color** | Used for buttons and accents. | | **Powered by Rectify** | **Keep** or **Hide** the Rectify badge. Hiding it needs the Launch plan or above. | Under **Sending domain**, you can send from your own address instead of Rectify's. Connect Resend under **Project settings**, **Integrations** first, then turn on: - **Changelog and Quanta emails**: changelog updates to subscribers, and emails Quanta sends for you. - **Project emails**: feedback, chat, mention and portal sign-in emails. If your Resend account fails, these fall back to Rectify, so sign-ins keep working. Until then, emails come from **Rectify** at support@mail.rectify.so. Mail sent from your own domain has no delivery tracking in Rectify. Select **Save** in the bar at the bottom to keep your changes. ## Check it worked Open **Templates** and select the email. The preview shows your new subject, message, logo and colour. Rows you switched off show **Off**. ### It says "Removing the Rectify badge is on the Launch plan and above" Your plan doesn't include hiding the badge. Upgrade to Launch or above, or keep **Powered by Rectify** on **Keep**. ### The Sending domain switches are greyed out Resend isn't connected to this project. Connect it under **Project settings**, **Integrations**. ### "Pick an image under 4 MB" The logo is too big. Use a JPG, PNG or GIF under 4 MB. To send your own emails to your contacts, use **Messaging** under **Customers** instead. --- # How integrations work Collection: Integrations URL: https://app.rectify.so/rectify/help/a/61-how-integrations-work What each integration does, when Rectify sends things to your other tools, who can connect them, and how to pause or disconnect one. > **Note:** **Before you start.** Integrations don't need a paid plan. Everyone who can open a project can connect, change and pause its integrations. Only Owners and Admins can disconnect one. Resend goes further: only Owners and Admins can connect it, turn it on or off, or remove it. Integrations connect a Rectify project to the tools your team already uses, such as GitHub, Jira or Slack. Each project has its own: connecting Slack in one project doesn't connect it in your other projects. ## Find your integrations Open **Project settings**, then **Integrations**. ![1 Search integrations. 2 Connected. 3 The selected integration.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106382122-01-page.png) The list on the left has every integration: - **Search integrations** finds one by its name, what it does, its group, or a feature it works with, such as "Workflow". - **Connected** sits at the top and holds everything connected in this project. Each one shows its setting, such as a repository or project, and whether it's **On** (green dot) or **Paused** (amber dot). - The rest are grouped into **Issues and code**, **Messages and alerts**, **Automation** and **Customer tools**. Select an integration to open it on the right. Until it's connected, you see **Connect** and a **Works with** card that lists where it shows up in Rectify. Once it's connected, you see its status, its settings and a way to disconnect it. ## What each integration does | **Integration** | **What it does** | | --- | --- | | **GitHub** | Opens an issue for each new feedback report, lets Quanta read your code to triage bugs and open fix pull requests, and powers Code Scan. | | **GitLab** | Opens an issue in your GitLab project for each new report. | | **Jira** | Opens a Bug in your Jira project for each new report. | | **Linear** | Opens an issue in your Linear project for each new report. | | **Trello** | Adds a card to the To do list on your board for each new report. | | **Asana** | Adds a task to your Asana project for each new report. | | **Monday** | Adds an item to your Monday board for each new report. | | **Notion** | Adds each new report as a row in your Notion feedback database. | | **Slack** | Posts new feedback, or the events you pick, to a channel, and sends alerts from **Automation**. | | **Discord** | Takes ideas and bug reports from your Discord server, posts cards for public requests and changelog entries to channels you pick, DMs the people who follow a request, and answers support chats. | | **Twilio** | Lets Quanta call or text you about critical alerts and answer calls to your number. | | **Resend** | Sends email campaigns, emails to contacts, project emails and Quanta's emails from your own domain. | | **Webhook** | Sends each new report, or the events you pick, to your own URLs. | | **Zapier** and **Pabbly** | Start your Zaps or Pabbly workflows from each new report. | | **Intercom** and **HubSpot** | Open a ticket for each new report. | Each integration has its own setup guide: - [Connect GitHub](/rectify/help/a/62-connect-github), [Connect GitLab](/rectify/help/a/63-connect-gitlab), [Connect Jira](/rectify/help/a/64-connect-jira) and [Connect Linear](/rectify/help/a/65-connect-linear) - [Connect Trello, Asana or Monday.com](/rectify/help/a/66-connect-trello-asana-or-monday) and [Connect Notion](/rectify/help/a/67-connect-notion) - [Connect Slack](/rectify/help/a/68-connect-slack) and [Use your own Twilio and Resend accounts](/rectify/help/a/72-use-your-own-twilio-and-resend-accounts) - [Connect Discord](/rectify/help/a/132-connect-discord), [Collect ideas and bug reports from Discord](/rectify/help/a/133-collect-ideas-and-bug-reports-from-discord) and [Share roadmap and changelog updates in Discord](/rectify/help/a/134-share-roadmap-and-changelog-updates-in-discord) - [Connect Zapier or Pabbly Connect](/rectify/help/a/69-connect-zapier-or-pabbly-connect) - [Connect Intercom](/rectify/help/a/70-connect-intercom) and [Connect HubSpot](/rectify/help/a/71-connect-hubspot) Most of the integrations that create issues, cards or tasks also add a step to **Workflows**, such as **Create Jira Issue** or **Send to Slack**. The step uses the same connection and the same project, board or channel. ## When Rectify sends things - **Issue trackers and task tools** get each new feedback report once, as soon as it arrives. Every type of report is sent. Changes made later, in Rectify or in the other tool, aren't synced either way. - **Slack** and **Webhook** send each new report by default. You can pick other events instead, such as a status change or a new contact. - **Workflow steps** only send something when a workflow runs. - **Discord** works both ways. People in your server send ideas and bug reports into Rectify, and Rectify posts cards and changelog entries and sends DMs as things change. Reports that arrived before you connected an integration aren't sent. ## Pause or disconnect an integration ![1 The On and Off switch. 2 Disconnect.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106385715-02-pane.png) - **Pause:** turn the switch at the top of the integration to **Off**. Nothing is sent, and workflow steps that use it fail, until you turn it back **On**. Your settings stay as they are, and the list shows **Paused**. - **Disconnect:** select **Disconnect** at the bottom. The integration and its settings are removed from this project straight away, with no confirmation. You can connect it again any time. Only Owners and Admins see **Disconnect**. ## Troubleshooting ### I connected a tool but nothing arrives Check that the integration shows **On** in the list, and that its settings point where you expect, such as the right repository or project. The account you connected with must be able to create issues there. Only reports that arrive after you connect are sent. ### A workflow run fails with "... integration not enabled for this project" The integration the step uses is turned off or isn't connected in this project. Turn it **On**, or connect it, and run the workflow again. ### Resend's buttons are greyed out Only Owners and Admins can connect Resend, turn it on or off, or remove it. Ask one of them to do it. ### I don't see Disconnect Only Owners and Admins can disconnect an integration. Ask one of them, or turn the integration **Off** to pause it. ## Read next - [Connect GitHub](/rectify/help/a/62-connect-github) - [Connect Slack](/rectify/help/a/68-connect-slack) - [How feedback reaches your inbox](/rectify/help/a/25-how-feedback-reaches-your-inbox) --- # Connect GitHub Collection: Integrations URL: https://app.rectify.so/rectify/help/a/62-connect-github Install the Rectify app on GitHub so new feedback opens issues in your repository, and Quanta and Code Scan can read your code. > **Note:** **Before you start.** You need to be able to install apps on the GitHub account or organization that owns your repository. Everyone who can open the project can connect GitHub, on every plan. Some features that use GitHub have their own limits: Code Scan isn't on the free Idea plan, and only Owners and Admins can ask Quanta to write a fix. With GitHub connected to a project, Rectify can: - Open an issue in your feedback repository for each new feedback report. - Let Quanta read your code when it triages a bug, and open a draft pull request with a fix. - Check your repositories with Code Scan. - Open issues from a workflow with the **Create GitHub Issue** step. GitHub is connected per project. To use it in another project, connect it there too. ## Connect GitHub 1. Open **Project settings**, then **Integrations**. 2. Select **GitHub**. 3. Select **Connect**. GitHub opens. ![2 GitHub. 3 Connect.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106388412-01-connect.png) 4. Choose the GitHub account or organization to install the Rectify app on. 5. Choose which repositories Rectify can see: all of them, or only the ones you pick. 6. Approve the install. GitHub sends you back to **GitHub** in **Integrations**, now marked **Connected**. Rectify only sees the repositories you chose, and it only changes code when you ask Quanta for a fix. ## Choose the feedback repository Rectify starts with the first repository GitHub shares. To use another one: 1. Pick it under **Feedback repository**. 2. Select **Save**. You see **GitHub repository configured successfully**. ![1 Feedback repository. 2 Save.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106390475-02-repository.png) From then on, each new feedback report opens an issue in that repository, as soon as it arrives. The report's title becomes the issue title and its description becomes the issue body. Every type of report is sent: bugs, ideas, general feedback and testimonials. Changes made later, in Rectify or on GitHub, aren't synced either way. The **Create GitHub Issue** workflow step opens issues in the same repository. ## Choose the repository Quanta reads Quanta's triage, its fixes and its answers about your code use a second setting, which also starts as the first repository GitHub shares. If you connected GitHub in the setup wizard, both settings use the repository you picked there. 1. Open **Quanta** and select the GitHub button under the message box. It shows the repository Quanta reads now. 2. Pick the **Repository**. 3. Select **Save**. You see **Repository configured**. ![2 Repository. 3 Save.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106393289-03-quanta-repository.png) You can open the same window from a bug's Quanta triage panel. The **CodeScan** page asks for a repository and a branch each time you start a scan. ## Pause or disconnect GitHub To pause, turn the switch at the top of the GitHub page to **Off**. New reports stop opening issues and the **Create GitHub Issue** step stops working. Quanta and Code Scan can still read your code. Turn it back **On** to start again. To disconnect, select **Disconnect** under **Disconnect GitHub**. It happens straight away, with no confirmation, and you see **GitHub integration removed successfully**. > **Note:** Disconnecting only affects this project. Other Rectify projects that use the same GitHub account or organization stay connected. When no other project uses it, Rectify also uninstalls its app from that GitHub account or organization. ## Troubleshooting ### It says "Failed to fetch repositories, please try re-authenticating with your GitHub account." Rectify can't reach GitHub with this connection, for example because the app was uninstalled or its access changed on GitHub. You may also see "GitHub no longer accepts this project's connection. Reconnect GitHub in Integrations." Open the GitHub window in **Quanta** and select **Reconnect**, then approve Rectify on GitHub again. ### My repository isn't in the list Rectify only sees the repositories you gave the Rectify app on GitHub. Add the repository to the app's access in your GitHub settings, then come back and pick it. ### No issues appear on GitHub Check that GitHub shows **On** in **Integrations** and that **Feedback repository** is the one you expect. Only reports that arrive after you connect are sent. ### A workflow run fails with "GitHub integration not enabled for this project" GitHub is turned off or not connected in this project. Turn it **On**, or connect it, and run the workflow again. ## Read next - [How integrations work](/rectify/help/a/61-how-integrations-work) - [Triage and fix bugs with Quanta](/rectify/help/a/28-triage-and-fix-bugs-with-quanta) - [What Quanta can do](/rectify/help/a/34-what-quanta-can-do) --- # Connect GitLab Collection: Integrations URL: https://app.rectify.so/rectify/help/a/63-connect-gitlab Connect your GitLab.com account so each new feedback report opens an issue in the GitLab project you choose. > **Note:** **Before you start.** Rectify works with GitLab.com. Self-managed GitLab isn't supported. You need a GitLab.com account that can create issues in the project you want to use. Everyone who can open the Rectify project can connect GitLab, on every plan. With GitLab connected to a project: - Each new feedback report opens an issue in your GitLab project. The report's title and description become the issue's title and description. - The **Create GitLab Issue** workflow step adds issues to the same project. GitLab is connected per project. To use it in another project, connect it there too. ## Connect GitLab 1. Open **Project settings**, then **Integrations**. 2. Select **GitLab**. 3. Select **Connect**. GitLab.com opens. ![2 GitLab. 3 Connect.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106395935-01-connect.png) 4. Sign in to GitLab, if it asks. 5. Check what Rectify asks for and authorize it. GitLab then sends you back to **GitLab** in **Integrations**, now marked **Connected**. ## Choose the GitLab project Rectify starts with the first of your own projects. To use another one: 1. Pick it under **GitLab project**. The list has your own projects and the projects in your GitLab groups. 2. Select **Save**. You see **GitLab project configured successfully**. ![1 GitLab project. 2 Save.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106398072-02-project.png) From then on, each new feedback report opens an issue in that project as soon as it arrives. Every type of report is sent. Changes made later, in Rectify or in GitLab, aren't synced either way. ## Pause or disconnect GitLab To pause, turn the switch at the top of the GitLab page to **Off**. New reports stop opening issues and the **Create GitLab Issue** step stops working until you turn it back **On**. To disconnect, select **Disconnect** under **Disconnect GitLab**. It happens straight away, with no confirmation, and you see **GitLab integration removed successfully**. Rectify forgets the connection but doesn't withdraw the access you gave it on GitLab. To withdraw that too, revoke Rectify under the authorized applications in your GitLab settings. ## Troubleshooting ### No issues appear in GitLab Check that GitLab shows **On** in **Integrations**, and that **GitLab project** is the one you expect. The GitLab account you connected with must be able to create issues in that project. Only reports that arrive after you connect are sent. ### My GitLab project isn't in the list The list shows the projects your GitLab.com account owns and the projects in groups you belong to. A project you were added to on its own, outside one of your groups, doesn't show. Ask for access to its group, then come back and pick it. ### A workflow run fails with "GitLab integration not enabled for this project" GitLab is turned off or not connected in this project. Turn it **On**, or connect it, and run the workflow again. ## Read next - [How integrations work](/rectify/help/a/61-how-integrations-work) - [Connect GitHub](/rectify/help/a/62-connect-github) - [Connect Slack](/rectify/help/a/68-connect-slack) --- # Connect Jira Collection: Integrations URL: https://app.rectify.so/rectify/help/a/64-connect-jira Connect your Jira Cloud site so each new feedback report opens a Bug in the Jira project you choose. > **Note:** **Before you start.** Rectify works with Jira Cloud. You need an Atlassian account that can create issues in the Jira project you want to use, and the project needs the **Bug** issue type. Everyone who can open the Rectify project can connect Jira, on every plan. With Jira connected to a project: - Each new feedback report opens a **Bug** in your Jira project, whatever its type in Rectify. The report's title becomes the summary and its description becomes the description. - The **Create Jira Issue** workflow step adds a **Task** to the same Jira project. Jira is connected per project. To use it in another project, connect it there too. ## Connect Jira 1. Open **Project settings**, then **Integrations**. 2. Select **Jira**. 3. Select **Connect**. Atlassian opens. ![2 Jira. 3 Connect.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106400881-01-connect.png) 4. Sign in to Atlassian, if it asks. 5. Check what Rectify asks for and approve it. Rectify asks to read and create Jira issues, read your Jira profile, and keep access while you're away, so it can send reports at any time. Atlassian then sends you back to **Jira** in **Integrations**, now marked **Connected**. ## Choose the Jira project Rectify starts with the first project it finds in your Jira site. To use another one: 1. Pick it under **Jira project**. Each project shows its name and key, for example **Acme Web (WEB)**. 2. Select **Save**. You see **Jira project configured successfully**. ![1 Jira project. 2 Save.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106402530-02-project.png) From then on, each new feedback report opens a Bug in that project as soon as it arrives. Changes made later, in Rectify or in Jira, aren't synced either way. The list in **Integrations** shows the project's key, for example **Project WEB**. ## Pause or disconnect Jira To pause, turn the switch at the top of the Jira page to **Off**. New reports stop opening Bugs and the **Create Jira Issue** step stops working until you turn it back **On**. To disconnect, select **Disconnect** under **Disconnect Jira**. It happens straight away, with no confirmation, and you see **Jira integration removed successfully**. Rectify forgets the connection but doesn't withdraw the access you gave it in Atlassian. To withdraw that too, remove Rectify from the apps connected to your Atlassian account. ## Troubleshooting ### No Bugs appear in Jira Check that Jira shows **On** in **Integrations**, and that **Jira project** is the one you expect. The project needs the **Bug** issue type, and the Atlassian account you connected with must be able to create issues in it. Only reports that arrive after you connect are sent. ### My Jira project isn't in the list The list shows the projects your Atlassian account can see on one Jira site. Rectify uses the first site Atlassian gives it access to, so if you work on more than one site, the project may be on another one. ### A workflow run fails with "Jira integration not enabled for this project" Jira is turned off or not connected in this project. Turn it **On**, or connect it, and run the workflow again. ## Read next - [How integrations work](/rectify/help/a/61-how-integrations-work) - [Connect Linear](/rectify/help/a/65-connect-linear) - [Connect Slack](/rectify/help/a/68-connect-slack) --- # Connect Linear Collection: Integrations URL: https://app.rectify.so/rectify/help/a/65-connect-linear Connect Linear so each new feedback report opens an issue, with its priority, in the Linear project you choose. > **Note:** **Before you start.** You need a Linear account that can create issues, and at least one project in your Linear workspace: Rectify adds issues to a project, not straight to a team. Everyone who can open the Rectify project can connect Linear, on every plan. With Linear connected to a project: - Each new feedback report opens an issue in your Linear project, in that project's team. The report's title and description become the issue's title and description, and its priority carries over. - The **Create Linear Issue** workflow step adds issues to the same project. Issues are created as the person who connected Linear. Linear is connected per project, so to use it in another project, connect it there too. ## Connect Linear 1. Open **Project settings**, then **Integrations**. 2. Select **Linear**. 3. Select **Connect**. Linear opens. ![2 Linear. 3 Connect.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106405313-01-connect.png) 4. Check what Rectify asks for and approve it. Rectify asks to read your workspace and create issues. Linear then sends you back to **Linear** in **Integrations**, now marked **Connected**. ## Choose the Linear project Rectify starts with the first project it finds in your workspace. To use another one: 1. Pick it under **Linear project**. 2. Select **Save**. You see **Linear integration configured successfully**. ![1 Linear project. 2 Save.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106406964-02-project.png) If a project belongs to more than one team, issues go to the first team Linear lists for it. ## How priorities carry over | **Priority in Rectify** | **Priority in Linear** | | --- | --- | | **Critical** | Urgent | | **High** | High | | **Medium** | Medium | | **Low** | Low | | **Neutral** | No priority | Each report is sent once, as soon as it arrives. Changes made later, in Rectify or in Linear, aren't synced either way. ## Pause or disconnect Linear To pause, turn the switch at the top of the Linear page to **Off**. New reports stop opening issues and the **Create Linear Issue** step stops working until you turn it back **On**. To disconnect, select **Disconnect** under **Disconnect Linear**. It happens straight away, with no confirmation, and you see **Linear integration removed successfully**. Rectify forgets the connection but doesn't withdraw the access you gave it in Linear. To withdraw that too, remove Rectify from the apps you've authorized in your Linear settings. ## Troubleshooting ### No issues appear in Linear Check that Linear shows **On** in **Integrations**, and that **Linear project** is the one you expect. Only reports that arrive after you connect are sent. ### The Linear project list is empty Your workspace has no projects yet, or your Linear account can't see them. Create a project in Linear, then come back and pick it. ### A workflow run fails with "Linear project or team not configured" Pick a project under **Linear project** and select **Save**, then run the workflow again. ### A workflow run fails with "Linear integration not enabled for this project" Linear is turned off or not connected in this project. Turn it **On**, or connect it, and run the workflow again. ## Read next - [How integrations work](/rectify/help/a/61-how-integrations-work) - [Connect Jira](/rectify/help/a/64-connect-jira) - [Connect Slack](/rectify/help/a/68-connect-slack) --- # Connect Trello, Asana or Monday.com Collection: Integrations URL: https://app.rectify.so/rectify/help/a/66-connect-trello-asana-or-monday Turn every new feedback report into a Trello card, an Asana task or a Monday.com item on the board or project you pick. > **Note:** **Before you start.** You need an account in the tool you're connecting, with access to the board or project you want to use. Owners, Admins and Members who can open the project can connect these tools. Integrations are on every plan, and each project connects its own accounts. Each of these tools gets a new entry for every new feedback report. Entries only go one way: what you change in the tool doesn't come back to Rectify. | **Tool** | **What each report becomes** | | --- | --- | | **Trello** | A card at the top of the **To do** list on your board, with the report's title as its name and the description inside | | **Asana** | A task in your project, with the report's title as its name and the description in its notes | | **Monday** | An item on your board, named after the report's title | You can connect one, two or all three. ## Connect the tool 1. Open **Project settings**, then **Integrations**. 2. Select **Trello**, **Asana** or **Monday** under **Issues and code**. 3. Select **Connect**. ![2 Trello, Asana or Monday. 3 Connect.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106409549-01-connect.png) 4. The tool opens. Sign in if it asks and allow Rectify access. 5. You're sent back to **Integrations**, where the tool now shows **Connected**. When you connect, Rectify picks your first board, or your first workspace and project, for you. Check it in the next step. ## Choose where entries go **Trello:** 1. Under **Trello board**, pick a board. 2. Select **Save**. Rectify adds cards to the list named **To do** on that board. If the board has no list with exactly that name, Rectify creates one. **Asana:** 1. Under **Asana project**, pick a **Workspace**. 2. Pick a **Project** in that workspace. 3. Select **Save**. **Monday:** 1. Under **Monday board**, pick a **Workspace**. 2. Pick a **Board** in that workspace. 3. Select **Save**. ## Use it in workflows Workflows can add entries to the same board or project as part of their steps: - **Create Trello Card** adds a card to your Trello board. - **Create Asana Task** adds a task to your Asana project. - **Create Monday Item** adds an item to your Monday board. The step only works while the tool is connected and switched on. Add it to a workflow from **Project settings**, **Workflows**. ## Pause or disconnect - **Pause:** turn off the switch next to **On** at the top of the tool's settings. The tool shows **Paused**, and new reports and workflow steps stop sending to it. Reports that arrive while it's paused aren't sent later. - **Disconnect:** select **Disconnect** under **Disconnect Trello**, **Disconnect Asana** or **Disconnect Monday**. This removes the tool and its board or project choice from the project. Cards, tasks and items already created stay where they are. To take away Rectify's access on the tool's side too, remove Rectify from the connected apps in that tool's settings. ## Check it worked Send a test report from your widget, then open your board or project. The report appears as a new card, task or item. In **Integrations**, the tool reads **Board selected** or **Project selected** under its name. ### A second To do list appeared on my Trello board Rectify looks for a list named exactly **To do**, with a small "d". If your list is called "To Do" or something else, Rectify makes its own. Rename your list to **To do** and delete the extra one, and new cards go to yours. ### My board or project isn't in the list The lists show what the account you connected with can open. Ask for access in the tool, or select **Disconnect** and connect again with an account that has it. ### A workflow step fails with "Trello integration not enabled for this project" The tool isn't connected, or it's paused. Asana and Monday say the same with their own names. Open **Integrations**, connect the tool or turn its switch back on, and run the workflow again. ## Read next - [How integrations work](/rectify/help/a/61-how-integrations-work) - [Connect Notion](/rectify/help/a/67-connect-notion) --- # Connect Notion Collection: Integrations URL: https://app.rectify.so/rectify/help/a/67-connect-notion Add every new feedback report as a row in a Notion database that Rectify creates for you. > **Note:** **Before you start.** You need a Notion account that can edit the page where the feedback database should go. Owners, Admins and Members who can open the project can connect Notion. Integrations are on every plan, and each project connects its own Notion. Once Notion is connected, each new feedback report becomes a row in a Notion database. Rectify creates the database for you under a page you choose and names it after your project, for example **Acme App Feedback**. Rows only go one way: what you change in Notion doesn't come back to Rectify. ## Connect Notion 1. Open **Project settings**, then **Integrations**. 2. Select **Notion** under **Issues and code**. 3. Select **Connect**. ![2 Notion. 3 Connect.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106412208-01-connect.png) 4. Notion opens. Sign in if it asks, choose the pages Rectify may use, and allow access. 5. Notion sends you back to **Integrations**, where Notion now shows **Connected**. Right after you connect, Rectify picks the first page it can see and creates the database there. Check that page in the next step. ## Choose where the database lives 1. Under **Notion database**, open **Page** and pick a page. 2. Rectify creates the database under that page straight away, and shows its name under **Database**. 3. Select **Save**. New reports now go to that database. The **Page** list only shows pages Rectify can see, which are the ones you allowed when you connected. If the page you pick already holds a database with **Title**, **Description**, **Status**, **Type** and **Priority** columns, Rectify uses it instead of creating another. ## What each row holds | **Column** | **What it holds** | | --- | --- | | **Title** | The report's title | | **Description** | The report's description, up to 2,000 characters | | **Type** | bug, idea, general or testimonial | | **Status** | open, in-progress, under-review or resolved | | **Priority** | low, medium, high, critical or neutral | | **Rating** | The star rating, if the person left one | | **Reporter** | The name of the person who sent it | | **Submitted at** | When it was sent | Each row is a copy of the report as it arrived. Later changes in Rectify, like a new status, aren't copied to Notion. ## Pause or disconnect Notion - **Pause:** turn off the switch next to **On** at the top of the Notion settings. Notion shows **Paused**, and new reports stop going to the database. Reports that arrive while it's paused aren't sent later. - **Disconnect:** select **Disconnect** under **Disconnect Notion**. This removes Notion and its settings from the project. The database and its rows stay in Notion. To take away Rectify's access on the Notion side too, remove Rectify from the connections in your Notion settings. ## Check it worked Send a test report from your widget, then open the database in Notion. The report appears as a new row. In **Integrations**, Notion shows **Database ready** under its name. ### The page I want isn't in the Page list Rectify only sees the pages you allowed when you connected. Select **Disconnect** under **Disconnect Notion**, then connect again and allow that page in Notion. ### Reports stop showing up in Notion Check that Notion says **Connected**, not **Paused**, and that **Database** shows a name. Rectify writes to the columns listed above, so renaming or deleting one of them in Notion stops new rows from being added. Change the column back to its first name and type. ## Read next - [How integrations work](/rectify/help/a/61-how-integrations-work) - [Connect Trello, Asana or Monday.com](/rectify/help/a/66-connect-trello-asana-or-monday) --- # Connect Slack Collection: Integrations URL: https://app.rectify.so/rectify/help/a/68-connect-slack Post new feedback, or the events you choose, to a Slack channel, and use the same channel for workflow steps and alerts. > **Note:** **Before you start.** You need to be able to add apps to your Slack workspace. Everyone who can open the Rectify project can connect Slack and choose what it posts, on every plan. With Slack connected to a project, Rectify posts to one channel you choose: - A message for each new feedback report, or only the events you pick. - The message from each **Send to Slack** workflow step. - The alerts you set up under **Automation**, **Slack alerts**. Slack is connected per project. To post another project's feedback, connect Slack in that project too. ## Connect Slack 1. Open **Project settings**, then **Integrations**. 2. Select **Slack**. 3. Select **Connect**. Slack opens. ![2 Slack. 3 Connect.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106415067-01-connect.png) 4. Pick the workspace and the channel Rectify should post to. 5. Approve the app. Slack sends you back to **Slack** in **Integrations**, now marked **Connected**, and Rectify joins the channel. Rectify asks Slack to post messages, to add a webhook to the channel you pick, and to join public channels. ## Choose what posts to Slack Out of the box, Rectify posts a message for each new feedback report. It shows the report's type, title, description, status, priority and rating, who sent it and when, whether it has a video, screenshots or a file, and the browser, system and page it came from. To pick other events: 1. Under **Notifications**, tick the events you want. 2. Select **Save**. You see **Slack notifications updated**. ![1 Events. 2 Save.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106416915-02-notifications.png) | **Group** | **Events** | | --- | --- | | **Feedback** | **New feedback submitted**, **Feedback status changed**, **Feedback assigned** | | **Contacts** | **Visitor becomes a contact**, **Contact enters a segment**, **Contact leaves a segment**, **Lead score crosses a band** | | **Behaviour** | **Form submitted**, **Survey answered** | | **Help Center** | **Help article published**, **Help article rated**, **Help search found nothing** | > **Important:** Once you tick any event, only the ticked events post. To keep a message for each new report, tick **New feedback submitted** too. Untick everything to go back to the default. Messages for ticked events are one line, for example "New bug [high] from Ada: Checkout button does nothing". Critical and high priorities show in brackets. An event you've already built an alert for under **Automation**, **Slack alerts** is skipped here, so the same event never posts twice. ## Change the channel Rectify posts to the channel you picked when you connected. To use another channel, disconnect Slack and connect it again, picking the new channel. Disconnecting also clears your **Notifications** choices, so tick them again afterwards. ## Pause or disconnect Slack To pause, turn the switch at the top of the Slack page to **Off**. Everything this project sends to Slack stops: feedback, events, **Send to Slack** steps and Slack alerts. Turn it back **On** to start again. To disconnect, select **Disconnect** under **Disconnect Slack**. It happens straight away, with no confirmation, and you see **Slack integration removed successfully**. The Rectify app stays in your Slack workspace until you remove it there. ## Troubleshooting ### New feedback stopped posting If you ticked any events under **Notifications**, only those post. Tick **New feedback submitted**, or untick everything, and select **Save**. ### Nothing posts at all Check that Slack shows **On** in **Integrations**. If the channel was archived or Rectify was removed from your workspace, disconnect Slack and connect it again. ### Slack alerts says "Slack is not connected" Alerts post to the channel you connect here. Select **Connect** on that message, which opens Slack in **Integrations**. ### A workflow run fails with "Slack integration not enabled for this project" Slack is turned off or not connected in this project. Turn it **On**, or connect it, and run the workflow again. ## Read next - [How integrations work](/rectify/help/a/61-how-integrations-work) - [Connect GitHub](/rectify/help/a/62-connect-github) - [How feedback reaches your inbox](/rectify/help/a/25-how-feedback-reaches-your-inbox) --- # Connect Discord Collection: Integrations URL: https://app.rectify.so/rectify/help/a/132-connect-discord Add Rectify to your Discord server so your community can send ideas and bug reports, and choose what Rectify posts back. > **Note:** **Before you start.** You need the **Manage Server** permission in the Discord server, which Discord asks for when you add an app. Everyone who can open the Rectify project can connect Discord and change its settings, on every plan. Only Owners and Admins can disconnect it. A project connects one server, and a server can only be connected to one project. With Discord connected to a project: - People in your server send ideas with `/feedback` and bug reports with `/bug`, and moderators send any message with **Send to Rectify**. - Ideas land on your roadmap and bug reports in your inbox, where only your team sees them. - Rectify can post a card for each public request and each changelog entry to channels you pick, and DM the people who follow a request when it moves or ships. ## Add Rectify to your server 1. Open **Project settings**, then **Integrations**. 2. Select **Discord**, under **Messages and alerts**. 3. Select **Add to Discord**. Discord opens. ![2 Discord. 3 Add to Discord.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794938269847-01-add.png) 4. Pick the server to add Rectify to. 5. Check the permissions and approve them. Discord sends you back to **Discord** in **Integrations**, now marked **Connected**, and you see "Discord is connected. People in your server can use /feedback and /bug now." Rectify asks Discord to view channels, send messages, embed links, attach files and read message history, so it can reply to people and post cards. It also asks to manage webhooks and threads, create private threads and send messages in threads, which support chats use. It adds the `/feedback`, `/bug` and `/support` commands and the **Send to Rectify** and **Move to support** message actions to your server. [Set up support chat in Discord](/rectify/help/a/131-set-up-support-chat-in-discord) covers the support ones. ## Choose where ideas and bug reports go Every change saves as soon as you make it. ![1 Board for new ideas. 2 Review before they go public.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794938272490-02-where.png) Under **Where feedback goes**: - **Board for new ideas:** the board `/feedback` starts on. People can pick another public board in the form. Only boards where everyone or signed-in people can post are listed, so private boards and boards limited to segments never take ideas from Discord. - **Bug reports:** always go to **Inbox › Feedback**, from `/bug` or from **Send to Rectify** as a bug. They're never public. - **Review before they go public:** on by default. Every new idea from Discord waits in your review queue until someone publishes it, with **Publish** in the queue or **Approve** on the post. Turn it off and ideas follow your portal's own review rules, where people from Discord count as signed in. ## Choose what Rectify posts in Discord ![1 Feedback board channel. 2 Changelog channel. 3 Updates by DM.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794938274750-03-posts.png) Under **What Rectify posts in Discord**: - **Feedback board channel:** a card for each public post, with **Upvote** and **Follow**. - **Changelog channel:** each changelog entry when it goes live, with a link to read it. - **Updates by DM:** on by default. Rectify DMs only the people who chose to follow a request or a bug report. Both channels start on **Not posting**. Only channels where Rectify can view the channel, send messages and embed links are listed, with their category next to the name. [Share roadmap and changelog updates in Discord](/rectify/help/a/134-share-roadmap-and-changelog-updates-in-discord) shows what the cards, posts and DMs look like. ## Who can use the commands Everyone in your server can use `/feedback` and `/bug`. **Send to Rectify** is for people who can manage messages. To change who can use each one, a server admin opens **Server Settings › Integrations › Rectify** in Discord. ## Pause or disconnect Discord To pause, turn the switch at the top of the Discord page to **Off**. While it's off, the commands reply "Rectify is paused in this server.", nothing is posted to your channels and no DMs go out. Nothing is sent later either. Your settings stay as they are, and the list shows **Paused**. Turn it back **On** to start again. Cards already in your board channel then catch up with the latest status and votes. To disconnect, an Owner or Admin selects **Disconnect** under **Disconnect Discord**. It happens straight away, with no confirmation, and you see **Discord disconnected**. The Discord settings are cleared, and Rectify leaves your server a few moments later. Posts, bug reports, votes and contacts stay in Rectify. Before it leaves, Rectify takes **Upvote**, **Follow** and **Share** off its cards, so nobody presses a button that can't work any more. **View on portal** stays. Cards and changelog posts stay in their channels, but they stop updating. ![Disconnect, at the bottom of the Discord page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794938277257-04-disconnect.png) ## If Rectify is removed from your server If someone removes Rectify in Discord, Rectify notices the next time it tries to reach your server, or in a daily check. The Discord page then shows **Removed from** and your server's name. ![1 Add it again. 2 Clear.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794938279058-05-removed.png) - **Add it again** adds Rectify back, to the same server or another one. Your board and both switches are kept. Pick the channels again, because they go back to **Not posting**. - **Clear** removes the old server and its settings from the project. Only Owners and Admins see it. You see **Removed server cleared**. ## Check it worked The Discord page shows your server's name with "Rectify is in this server.", and the list on the left shows **Discord** under **Connected**. In your server, type `/feedback`: the **Share an idea** form opens. [Collect ideas and bug reports from Discord](/rectify/help/a/133-collect-ideas-and-bug-reports-from-discord) explains what happens next. ## Troubleshooting ### It says "That server is connected to another project. Disconnect it there first." A Discord server can only be connected to one Rectify project. Disconnect it in the other project, or pick another server. ### It says "That link has expired. Click Add to Discord again." The link from **Add to Discord** lasts 10 minutes and works once. Select **Add to Discord** again and finish in Discord without a long wait. ### It says "Finish in the Rectify account that clicked Add to Discord." The browser you came back in is signed in to Rectify as someone else, or that person can no longer open the project. Sign in as the person who selected **Add to Discord**, then start again. ### It says "Discord was not connected." or "Discord could not be connected. Try again in a minute." The first means the permissions weren't approved in Discord. The second means something went wrong on the way back. In both cases nothing changed, so select **Add to Discord** again. ### A channel I want isn't in the list Rectify only lists text and announcement channels it can post in. In Discord, open **Edit Channel › Permissions** on that channel and allow **View Channel**, **Send Messages** and **Embed Links** for the Rectify role. If a channel you picked earlier loses these, it shows as **A channel Rectify cannot post in**. ### Board for new ideas is greyed out It says "No board takes ideas from Discord yet." Edit a board and let everyone or signed-in people post on it. A board whose **Submit form** has a question that is both **Required** and **Show the answer publicly** can't take ideas from Discord either, because the Discord form can't ask it. ### I don't see Disconnect Only Owners and Admins can disconnect Discord. Ask one of them, or turn the switch **Off** to pause it. ## Read next - [Collect ideas and bug reports from Discord](/rectify/help/a/133-collect-ideas-and-bug-reports-from-discord) - [Share roadmap and changelog updates in Discord](/rectify/help/a/134-share-roadmap-and-changelog-updates-in-discord) - [How integrations work](/rectify/help/a/61-how-integrations-work) --- # Collect ideas and bug reports from Discord Collection: Integrations URL: https://app.rectify.so/rectify/help/a/133-collect-ideas-and-bug-reports-from-discord How people in your Discord server send ideas with /feedback, bug reports with /bug and messages with Send to Rectify, and where each one lands. > **Note:** **Before you start.** Discord must be connected to your project, see [Connect Discord](/rectify/help/a/132-connect-discord). Everyone in your server can use `/feedback` and `/bug`. **Send to Rectify** is for people who can manage messages, unless a server admin changes it in Discord. Once Discord is connected, your community sends feedback without leaving Discord. Ideas become requests on your roadmap. Bug reports go to your inbox, where only your team sees them. ## Share an idea with /feedback In your server, someone types `/feedback` and the idea in a few words, then presses Enter. The **Share an idea** form opens with that title filled in. | **Field** | **What goes in it** | | --- | --- | | **Title** | The idea, 3 to 300 characters. | | **Details** | Optional, up to 4,000 characters. | | **Board** | Shown when more than one board takes ideas from Discord. It starts on your **Board for new ideas**. | | **Screenshots** | Optional, up to 5 images, videos or files. | | **Send me updates by DM** | Ticked to start with. It's only there while **Updates by DM** is on. | ## Report a bug with /bug Someone types `/bug` and what went wrong in a few words, then presses Enter. The **Report a bug** form opens. | **Field** | **What goes in it** | | --- | --- | | **What went wrong** | 3 to 100 characters. | | **What happened** | Optional, up to 500 characters. | | **Where** | Optional, up to 200 characters, such as a page, screen or feature. | | **Screenshots** | Optional, up to 5 images, videos or files. | | **DM me when it's fixed** | Ticked to start with. It's only there while **Updates by DM** is on. | ## Send a message with Send to Rectify When someone posts a good idea or a bug in a normal message, a moderator can send it to Rectify for them: 1. In Discord, open the message's menu: right-click it, or press and hold it on a phone. 2. Select **Apps**, then **Send to Rectify**. 3. Check the **Title**, which is the first line of the message (up to 100 characters), and the **Details**, which is the whole message. 4. Under **Type**, keep **Idea** or pick **Bug report**. 5. For an idea, pick a **Board** if there's more than one. 6. Submit the form. The item is credited to the person who wrote the message, not to the moderator, and the message's files come with it. Rectify replies under the original message so its author can follow it: "Priya Nair, the Acme App team has your idea. Follow it to get a DM when it moves." with a **Follow updates** button. Only the person who reported a bug can follow it. ## What people see after they send Rectify answers each person privately, so only they see the reply. With Acme App as the project: | **They sent** | **The reply** | | --- | --- | | An idea that waits for review | Thanks, Priya Nair. **Snooze a task until a later date** reached the Acme App team. They review new posts before they go public, and you'll get a DM when it moves. | | An idea that's public straight away | Thanks, Priya Nair. **Snooze a task until a later date** is on the Acme App roadmap now. You'll get a DM when it moves. A **View on portal** button opens it when your portal is public. | | A bug report | Thanks, Tomás Ortega. The Acme App team has your bug report: **Due date shows a day early in the calendar**. Only the team can see it, and you'll get a DM when it's fixed. | | Send to Rectify | Sent to Rectify as an idea: **Snooze a task until a later date**. Or "Sent to Rectify as a bug report". | The part about DMs only shows when they kept the DM box ticked. ## Where they land in Rectify - **Ideas** become requests on the board they picked. The person who sent it votes for it automatically and, if they ticked the box, follows it. With **Review before they go public** on, every idea waits in **Roadmap**, **Review queue** until someone publishes it. With it off, your portal's review rules decide, and people from Discord count as signed in. - **Bug reports** go to **Inbox**, **Feedback** as a **Bug**. The **Where** answer is added to the description. Images become the report's screenshots. Like any other report, they're also sent to the issue trackers you've connected. - Your team hears about both the same way as about posts from your portal and reports from your widget, and they start the same workflows. ## How they look in Rectify Open the request on your roadmap, or the report in **Inbox**, **Feedback**. ![1 The person, marked Discord member. 2 Source, Discord.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794938285988-01-idea.png) - The person who sent it shows with their Discord name, and **Discord member** where an email would be. - **Source** says **Discord**. Select it to open it in Discord. For **Send to Rectify**, that's the original message. For `/feedback` and `/bug`, it's the channel where the command was used. ![1 Tomás Ortega, Discord member. 2 Source, Discord, on a bug report.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794938288852-02-bug.png) To answer a bug report's author in Discord, use **Reply to user** on the report. It needs support chat in Discord, see [Set up support chat in Discord](/rectify/help/a/131-set-up-support-chat-in-discord). ## People from Discord become contacts Everyone who sends an idea or a bug report, or presses **Upvote** or **Follow** on a card, becomes a contact in your project, named after their Discord name. They have no email address, so Rectify reaches them by DM instead. One person stays one contact: their later ideas, reports and votes join the same record in **Contacts**. ## Limits | **Limit** | **What people see when they reach it** | | --- | --- | | 5 ideas or bug reports per person every 10 minutes | You have sent a lot in a short time. Try again in a few minutes. | | 300 ideas or bug reports per server each day | This server has sent a lot today. Try again tomorrow. | | 30 button presses per person a minute | That was a lot of clicks. Try again in a minute. | Each idea or bug report can bring up to 5 files: images, videos, PDFs and text files, up to 10 MB each. Files Rectify can't copy are named at the end of the reply, for example "Not attached: build.zip. Files can be images, videos, PDFs or text files up to 10 MB." **Send to Rectify** copies the first 5 files of the message. ## Check it worked In Rectify, open **Roadmap**, **Review queue** for ideas waiting for review, or **All posts** for public ones, and **Inbox**, **Feedback** for bug reports. Items from Discord show **Discord** next to **Source**. ## Troubleshooting ### People see "Rectify is paused in this server." Discord is switched **Off** in **Integrations**. Turn it back **On**. ### People see "This server is not taking ideas right now." No board can take ideas from Discord. Let everyone or signed-in people post on at least one board. [Connect Discord](/rectify/help/a/132-connect-discord) explains which boards qualify. ### People see "Rectify is not connected to this server yet." The server isn't connected to any Rectify project, or it was disconnected. Connect it from **Integrations** in Rectify. ### People see "Some answers were too short or too long." A title must be at least 3 characters. They should open the form again and check each answer against the limits above. ### A moderator sees "This form expired. Use Send to Rectify on the message again." The **Send to Rectify** form lasts 15 minutes. Use **Send to Rectify** on the message again. ### A moderator sees "Rectify cannot take messages sent by bots." **Send to Rectify** only works on messages written by people. ### I can't find Send to Rectify in Discord It's only shown to people who can manage messages. A server admin can change that in Discord under **Server Settings › Integrations › Rectify**. ### People see "Something went wrong on our side. Try again in a minute." Rectify tried a few times and couldn't finish saving it. Check **Review queue**, **All posts** or **Inbox**, **Feedback** first. If it isn't there, they can send it again in a minute. ## Read next - [Share roadmap and changelog updates in Discord](/rectify/help/a/134-share-roadmap-and-changelog-updates-in-discord) - [Moderate new posts in the review queue](/rectify/help/a/56-moderate-new-posts-in-the-review-queue) - [Triage feedback](/rectify/help/a/26-triage-feedback) --- # Share roadmap and changelog updates in Discord Collection: Integrations URL: https://app.rectify.so/rectify/help/a/134-share-roadmap-and-changelog-updates-in-discord Post a card for each public request and each changelog entry to your Discord server, and DM the people who follow a request when it moves or ships. > **Note:** **Before you start.** Discord must be connected to your project, see [Connect Discord](/rectify/help/a/132-connect-discord). Everyone who can open the project can pick the channels and turn DMs on or off. Cards, changelog posts and portal links need a public portal. Rectify can keep your Discord community in the loop in three ways, and you can use any of them: - **Board cards:** a card in a channel for each public request, with **Upvote** and **Follow**. - **Changelog posts:** each changelog entry in a channel when it goes live. - **DMs:** a direct message to the people who follow a request or a bug report. ## Pick the channels 1. Open **Project settings**, then **Integrations**, and select **Discord**. 2. Under **What Rectify posts in Discord**, open **Feedback board channel** or **Changelog channel**. 3. Pick a channel. It saves straight away. ![1 Changelog channel. 2 A channel to post in.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794938291846-01-channels.png) To stop posting, pick **Not posting**. You can use the same channel for both. ## Board cards Once a **Feedback board channel** is picked, Rectify posts a card for every request that becomes public from then on: when your team adds it, when you approve it in the review queue, when it's published straight away from your portal, widget or Discord, or when it moves to a board Discord can see. Requests that were already public aren't posted. Only requests on boards Discord can see get a card. That means your portal is public and everyone or signed-in people can view the board. Each card shows: - The request's title, which opens it on your portal, and who posted it. - The start of the request, up to 300 characters. - **Status**, **Votes** and **Board**, with the card coloured like the status. - Buttons: **Upvote**, **Follow**, **Share** and **View on portal**. **Upvote** shows when Discord people can vote on that board, and **Follow** shows while **Updates by DM** is on. The card keeps up with the request. When its status, votes or text change, Rectify updates the card within about 10 seconds. If the request is deleted, merged into another one or its board stops being visible, the card is removed from the channel. ### What the buttons do Rectify answers each press privately, so only that person sees the reply. | **Button** | **What happens** | **The reply** | | --- | --- | --- | | **Upvote** | Adds their vote, the same as a vote on your portal. | Upvoted. 13 votes now. | | **Follow** | They get a DM when the request moves or ships. | You'll get a DM when this moves. | | **Share** | Gives them links to pass on. | Share **Calendar view for tasks** with this link, followed by the portal link and a link to the card itself. | | **View on portal** | Opens the request on your portal. | | Upvoting doesn't follow a request. People who want DMs press **Follow**, or keep the DM box ticked when they send an idea. ## DMs to followers Rectify only DMs people who asked for it: they ticked **Send me updates by DM** or **DM me when it's fixed** in the form, or pressed **Follow** on a card or **Follow updates** under a message sent with **Send to Rectify**. | **The DM** | **When it's sent** | | --- | --- | | **Update on** and the request's title | You send an update to the request's followers after moving it to a status outside the **Completed** group. It carries your message. | | **Shipped:** and the request's title | You send an update after moving it to a **Completed** status, or a changelog entry that links it goes live. | | **Your post is live** or **Your post was not approved** | You approve or decline an idea they sent from Discord. | | **Fixed:** and the bug's title | You mark a bug report they sent as **Resolved**. It says "The Acme App team marked this as resolved. Thanks for reporting it." | Each DM is signed "From the Acme App team", with your project's name. It has a **View on portal** or **Read the changelog** button when your portal is public, and **Stop updates**, which unfollows that request or bug report. When you send an update from the follower update dialog, followers who came from Discord get it as a DM instead of an email. The dialog says how many. ![1 The line that counts followers who get a Discord DM.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794938294305-02-follower-dms.png) [Notify followers when you ship](/rectify/help/a/60-notify-followers-when-you-ship) covers the dialog itself. DMs only go out while Discord is **On** and **Updates by DM** is on. Turn **Updates by DM** off to stop them all: the DM boxes leave the forms, and **Follow** no longer shows on new or updated cards. If someone has turned off DMs from server members in Discord, Rectify skips them. ## Changelog posts Once a **Changelog channel** is picked, Rectify posts each changelog entry there when it goes live, at its scheduled time for a scheduled entry. The post shows: - **New in Acme App**, with your project's name, at the top. - The entry's title, which opens it on your portal. - The start of the entry, up to 300 characters. - "Requested by 3 people in this server", when people from your server voted for a request the entry links. - A **Read the changelog** button. Changelog posts follow the same rules as the changelog email: - An entry you publish without **Email subscribers** ticked is never posted. - **Resend email**, then **Send again**, posts it again. - Entries limited to segments, and entries on a private portal, are never posted. - Pausing changelog emails doesn't stop Discord posts. When you edit an entry after it's posted, the post in Discord changes too, within a few seconds. Move the entry back to draft, delete it or limit it to segments, and Rectify removes its post from Discord. Publishing it again doesn't post it again, the same way it doesn't email again. The followers of the requests it links who follow through Discord get a **Shipped** DM at the same time, even while changelog emails are paused. ## Check it worked Publish a test entry, or approve a request on a board Discord can see, and look in the channel you picked. In the follower update dialog, the line about Discord DMs shows how many followers came from Discord. ## Troubleshooting ### A public request didn't get a card Cards are only posted for requests that become public after you pick the channel, on boards Discord can see. Check that your portal is public and that everyone or signed-in people can view the board. Also check that Discord is **On**. ### A changelog entry didn't post It was published without **Email subscribers** ticked, it's limited to segments, or your portal is private. To post it now, Owners and Admins can open it and select **Resend email**, then **Send again**. ### People see "This server has DM updates turned off." **Updates by DM** is off. Turn it on in **Integrations**, **Discord**. ### People see "This post is waiting for review. You can follow it once it's public." Only the person who sent an idea can follow it while it waits in the review queue. Everyone else can follow it once you approve it. ### People see "Upvotes are closed for this post." or "This post is no longer here." The request was merged or deleted, or Discord people can't vote on its board. ### Someone didn't get a DM They need to follow the request, and their Discord privacy settings must allow DMs from server members. Rectify doesn't try again later. Also check that Discord is **On** and **Updates by DM** is on. ## Read next - [Notify followers when you ship](/rectify/help/a/60-notify-followers-when-you-ship) - [Write and publish a changelog post](/rectify/help/a/59-write-and-publish-a-changelog-post) - [Collect ideas and bug reports from Discord](/rectify/help/a/133-collect-ideas-and-bug-reports-from-discord) --- # Connect Zapier or Pabbly Connect Collection: Integrations URL: https://app.rectify.so/rectify/help/a/69-connect-zapier-or-pabbly-connect Start a Zap or a Pabbly Connect workflow from every new feedback report, and pass it on to thousands of other apps. > **Note:** **Before you start.** You need a Zapier or Pabbly Connect account. Owners, Admins and Members who can open the project can set these up. Integrations are on every plan, and each project sets up its own. Zapier and Pabbly Connect both start from Rectify: each new feedback report starts your Zaps or Pabbly Connect workflows, and they carry it on to your other apps. It only works in that direction. Zaps and workflows can't create or change anything in Rectify. ## Connect Zapier 1. Open **Project settings**, then **Integrations**, and select **Zapier** under **Automation**. 2. Select **Generate API key**. ![1 Zapier. 2 Generate API key.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106419712-01-zapier.png) 3. Under **API key**, select **Copy**. 4. In Zapier, start a Zap with Rectify as its trigger. When Zapier asks you to connect your account, paste the key. 5. Finish the Zap and turn it on. Each Zap you turn on signs up for this project's new reports, and turning a Zap off takes it away again. In **Integrations**, Zapier shows how many are signed up, for example **2 active Zaps**. When Zapier asks for test data, Rectify sends the project's latest feedback report, or a sample report if there isn't one yet. The key belongs to this project and stays the same. Anyone who has it can send the project's new reports to their own Zaps, so keep it private like a password. ## Connect Pabbly Connect 1. In Pabbly Connect, create a workflow that starts with a webhook, and copy its webhook URL. 2. In Rectify, open **Project settings**, then **Integrations**, and select **Pabbly** under **Automation**. 3. Paste the URL under **Webhook URLs**. 4. To send reports to another workflow too, select **Add webhook URL** and paste its URL. You can add up to 3. 5. Select **Save**. ![3 The webhook URL. 4 Add webhook URL. 5 Save.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106421608-02-pabbly.png) When you save, Rectify sends a sample report to each new URL, so Pabbly Connect can pick up the fields for your next steps. After that, every new feedback report goes to each URL. To stop sending to one workflow, select the bin next to its URL, then **Save**. ## What Rectify sends Each new report goes out as JSON with the report's details: - its title, description, type, status, priority and rating - the name and email of the person who sent it, if they gave them - the page it came from, with the browser, operating system and screen size - links to its screenshots, video and attachment, if it has any Rectify sends each report once, the moment it arrives. The requests aren't signed, and if your Zap or workflow doesn't answer, the report isn't sent again. If you need signed requests that are retried, use the webhooks under **Project settings**, **Automation**, **Webhooks** instead. ## Pause or disconnect - **Pause:** turn off the switch next to **On** at the top of the Zapier or Pabbly settings. Nothing is sent to your Zaps or workflows until you turn it back on, and reports that arrive in the meantime aren't sent later. - **Disconnect Pabbly Connect:** select **Disconnect** under **Disconnect Pabbly**. This removes all its URLs from the project. - **Stop a Zap:** turn the Zap off in Zapier. To stop every Zap at once, pause Zapier here. ## Check it worked Send a test report from your widget. In Zapier, the Zap's history shows a new run. In Pabbly Connect, the workflow's history shows the report arriving. ### It says "Enter a valid URL, including http:// or https://" Paste the full webhook URL from Pabbly Connect, starting with https://. ### It says "Duplicate URLs are not allowed" The same URL is in the list twice. Remove one of them with the bin, then select **Save**. ### I can't add a fourth Pabbly URL Each project can send to up to 3 Pabbly Connect URLs. Remove one you no longer use first. ### Zapier doesn't show any active Zaps Zaps sign up when you turn them on. Check the Zap is on in Zapier and that it uses the key from this project. Each project has its own key. ## Read next - [How integrations work](/rectify/help/a/61-how-integrations-work) - [Connect Notion](/rectify/help/a/67-connect-notion) --- # Connect Intercom Collection: Integrations URL: https://app.rectify.so/rectify/help/a/70-connect-intercom Open an Intercom ticket for every new feedback report, so your support team can follow it up there. > **Note:** **Before you start.** You need an Intercom workspace that uses tickets, and an Intercom teammate account to connect with. Owners, Admins and Members who can open the project can connect Intercom. Integrations are on every plan, and each project connects its own Intercom workspace. Once Intercom is connected, each new feedback report opens a ticket in Intercom with the report's title and description. Tickets only go one way: what you change in Intercom doesn't come back to Rectify. Each ticket is opened under the email address of the Intercom teammate who connected Rectify, not under the person who sent the feedback. That address shows under Intercom in the list of integrations. ## Connect Intercom 1. Open **Project settings**, then **Integrations**. 2. Select **Intercom** under **Customer tools**. You can also type its name in **Search integrations**. 3. Select **Connect**. ![2 Intercom. 3 Connect.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106424398-01-connect.png) 4. Intercom opens. Sign in if it asks and approve Rectify. 5. Intercom sends you back to **Integrations**, where Intercom now shows **Connected**. There's nothing else to set up. In the list, Intercom moves to **Connected** and shows the email of the teammate account you connected with. ## Pause or disconnect Intercom - **Pause:** turn off the switch next to **On** at the top of the Intercom settings. Intercom shows **Paused**, and new reports stop opening tickets. Reports that arrive while it's paused aren't sent later. - **Disconnect:** select **Disconnect** under **Disconnect Intercom**. This removes Intercom from the project. Tickets already in Intercom stay there. To take away Rectify's access on the Intercom side too, remove Rectify from the installed apps in your Intercom settings. ## Check it worked Send a test report from your widget, then open your tickets in Intercom. A new ticket with the report's title is there. ### I connected with the wrong Intercom account Tickets use the email of whoever connected. Select **Disconnect** under **Disconnect Intercom**, then ask the right teammate to select **Connect** and approve Rectify with their own Intercom account. ### I don't see the ticket Check that Intercom says **Connected**, not **Paused**, in **Integrations**, and that tickets are turned on in your Intercom workspace. ## Read next - [How integrations work](/rectify/help/a/61-how-integrations-work) - [Connect HubSpot](/rectify/help/a/71-connect-hubspot) --- # Connect HubSpot Collection: Integrations URL: https://app.rectify.so/rectify/help/a/71-connect-hubspot Open a HubSpot ticket for every new feedback report, so your support team sees it where they already work. > **Note:** **Before you start.** You need a HubSpot account that can create tickets. Owners, Admins and Members who can open the project can connect HubSpot. Integrations are on every plan, and each project connects its own HubSpot account. Once HubSpot is connected, each new feedback report opens a ticket in HubSpot. The ticket's name is the report's title and its description is the report's description. Tickets go into HubSpot's default support pipeline, at the **New** stage. Tickets only go one way: what you change in HubSpot doesn't come back to Rectify. Rectify asks HubSpot for access to tickets only. ## Connect HubSpot 1. Open **Project settings**, then **Integrations**. 2. Select **HubSpot** under **Customer tools**. You can also type its name in **Search integrations**. 3. Select **Connect**. ![2 HubSpot. 3 Connect.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106426949-01-connect.png) 4. HubSpot opens. Sign in if it asks, choose the HubSpot account to use, and approve Rectify. 5. HubSpot sends you back to **Integrations**, where HubSpot now shows **Connected**. There's nothing else to set up. In the list, HubSpot moves to **Connected** and reads **Account connected**. ## Pause or disconnect HubSpot - **Pause:** turn off the switch next to **On** at the top of the HubSpot settings. HubSpot shows **Paused**, and new reports stop opening tickets. Reports that arrive while it's paused aren't sent later. - **Disconnect:** select **Disconnect** under **Disconnect HubSpot**. This removes HubSpot from the project. Tickets already in HubSpot stay there. To take away Rectify's access on the HubSpot side too, remove Rectify from the connected apps in your HubSpot settings. ## Check it worked Send a test report from your widget, then open **Tickets** in HubSpot. A new ticket with the report's title is waiting in the **New** stage of your default support pipeline. ### I don't see the ticket Check that HubSpot says **Connected**, not **Paused**, in **Integrations**. Then look in HubSpot's default support pipeline: Rectify always adds tickets there, even if your team works in another pipeline. ### I connected the wrong HubSpot account Select **Disconnect** under **Disconnect HubSpot**, then select **Connect** again and choose the right account in HubSpot. ## Read next - [How integrations work](/rectify/help/a/61-how-integrations-work) - [Connect Intercom](/rectify/help/a/70-connect-intercom) --- # Use your own Twilio and Resend accounts Collection: Integrations URL: https://app.rectify.so/rectify/help/a/72-use-your-own-twilio-and-resend-accounts Connect Twilio for phone calls and text messages, and Resend for email campaigns and email from your own domain. > **Note:** **Before you start.** You need your own Twilio account, your own Resend account, or both. Owners, Admins and Members who can open the project can connect Twilio. Only Owners and Admins can connect, pause or disconnect Resend. Integrations are on every plan, and each project connects its own accounts. Phone call and SMS alert channels in **Monitoring** need the Launch plan or higher. Rectify doesn't make calls, send texts or send campaigns from an account of its own. These go through your Twilio and Resend accounts, so they come from your number and your domain, and you pay Twilio and Resend directly for what you send. | **Account** | **What Rectify uses it for** | | --- | --- | | **Twilio** | Quanta calling you about critical alerts, and calling you when you ask it to from a chat. Heartbeat calls and text messages. **Phone call** and **SMS** alert channels in **Monitoring**, **Alerting**. The **Make Phone Call** and **Send SMS** workflow steps. Calling Quanta from your phone. | | **Resend** | Email campaigns, which always send through Resend. Emails Quanta sends for you to people outside your team. Your changelog updates and project emails, if you switch them over. | ## Connect Twilio 1. Open **Project settings**, then **Integrations**. 2. Select **Twilio** under **Messages and alerts**. 3. Enter your **Account SID**. It starts with AC and is on the home page of your Twilio Console. 4. Enter your **Auth Token**, from the same page. 5. Enter your Twilio phone number under **From Number (E.164)**, with a plus and the country code, for example +15551234567. It must be a Twilio number that can make calls and send SMS. You'll find it in Twilio under **Phone Numbers**, **Manage**, **Active Numbers**. 6. Select **Connect**. ![3 Account SID. 4 Auth Token. 5 From Number (E.164). 6 Connect.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106429474-01-twilio.png) Twilio now shows **Connected**, with your Account SID and From Number. Rectify saves these details without testing them, so check them with a test call. [Talk to Quanta with your voice](/rectify/help/a/37-talk-to-quanta-with-your-voice) shows how to add your own number and place one. ### Let yourself call Quanta This part is optional. To call Quanta from your phone, point your Twilio number at Rectify: 1. In Twilio, open **Phone Numbers**, **Manage**, **Active Numbers** and select your number. 2. Under **Voice Configuration**, set **A call comes in** to **Webhook**. 3. Paste the address shown under **Incoming call webhook** on the Twilio page in Rectify, and choose **HTTP POST**. 4. Select **Save configuration**. Quanta only answers calls from the destination number saved in **Quanta Settings**, **Phone & SMS**, and only while **Enable phone alerts** is on there. ## Connect Resend Set up your sending domain in Resend first: 1. In Resend, add your domain under **Domains** and finish verifying it. 2. Under **API Keys**, create a key with **Full access**. Rectify uses it to track bounces and spam complaints on your campaigns. A sending-only key still sends, but those aren't tracked. Then connect it to Rectify: 1. Open **Project settings**, then **Integrations**. 2. Select **Resend** under **Messages and alerts**. 3. Paste your key under **API Key**. It starts with re_. 4. Enter the address to send from under **From Email**, on the domain you verified, for example hello@acme.example. 5. Optionally, enter the sender name under **From Name**, for example Acme. Without one, Rectify uses the name from your email branding. 6. Select **Connect**. ![3 API Key. 4 From Email. 5 From Name. 6 Connect.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106431093-02-resend.png) Rectify checks the key and the domain with Resend before it saves. Resend then shows **Connected**, with your From Email and From Name. ## Choose which emails send from your domain Email campaigns always send through Resend, so you can create them as soon as Resend is connected. For other emails, you choose: 1. Open **Project settings**, then **Email notifications**, and select **General**. 2. Under **Sending domain**, turn on what should send from your domain: - **Changelog and Quanta emails:** changelog updates to subscribers and emails Quanta sends for you. - **Project emails:** feedback, chat, mention and portal sign-in emails to your users. 3. Select **Save**. ![The two switches under Sending domain.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106432931-03-sending-domain.png) Emails you switch over aren't tracked for delivery and don't count in your email analytics. If Resend fails to send a project email, Rectify sends it instead, so sign-in codes keep arriving. ## Pause or disconnect - **Pause Resend:** turn off the switch next to **On** at the top of the Resend settings. Campaigns can't send while it's off, and your changelog and project emails go out from Rectify again. - **Disconnect Resend:** select **Disconnect** under **Disconnect Resend**. Rectify removes your key and the tracking it added to your Resend account. Campaigns can't send until you connect it again. - **Disconnect Twilio:** select **Disconnect** under **Disconnect Twilio**. Rectify removes your Twilio details, and calls and texts stop. ### It says "Account SID starts with AC followed by 32 characters" Copy the Account SID again from the home page of your Twilio Console. It's AC followed by 32 letters and numbers. ### It says "Use E.164 format, for example +15551234567" Enter the number with a plus and the country code, and no spaces or dashes. ### It says "Resend did not accept this API key. Check it and try again." The key was deleted or mistyped. Create a new key in Resend under **API Keys** and paste it again. ### It says the domain "is not added to your Resend account" or "is not verified in Resend yet" The **From Email** must be on a domain you've added and verified in Resend. Finish verifying it under **Domains** in Resend, then select **Connect** again. ### It says "Connect Resend in Integrations first, or turn it back on if it is off" You're sending a campaign while Resend isn't connected, or while it's paused. Connect Resend, or turn its switch back on, then send again. ### I can't type in the Resend fields Only Owners and Admins can connect Resend. Ask one of them to set it up. ## Read next - [Talk to Quanta with your voice](/rectify/help/a/37-talk-to-quanta-with-your-voice) - [Heartbeat: scheduled check-ins and urgent alerts](/rectify/help/a/38-heartbeat-check-ins-and-alerts) - [How integrations work](/rectify/help/a/61-how-integrations-work) --- # Widget JavaScript API reference Collection: Developers URL: https://app.rectify.so/rectify/help/a/80-widget-javascript-api-reference Every method on the Rectify widget, with what it takes and a working example, from init and control to track, identify and revenue. > **Note:** **Before you start.** The Rectify script must be on your site, and you need access to your site's code. `track`, `revenue` and `identify` send analytics events, so **Analytics** must be on for the project. The Rectify script defines two things on `window`: - `window.Rectify` is the widget class. - `window.RectifyInstance` is the widget running on your page. The install snippet creates it when the script loads. Call every method on `window.RectifyInstance`. The script loads after your page, so write `window.RectifyInstance?.` to skip the call safely if it isn't there yet. ```js window.RectifyInstance?.control('open'); window.RectifyInstance?.track('report_exported', { format: 'csv' }); ``` ## Methods at a glance | **Method** | **What it does** | | --- | --- | | `init(projectId, userInfo, config)` | Starts the widget. The install snippet calls it for you. | | `control(action, options)` | Opens, closes or toggles the widget, switches tab or opens a form. | | `registerShortcuts(shortcuts)` | Sets keyboard shortcuts from your code. | | `track(name, properties)` | Records a custom event. | | `revenue(amount, currency, properties)` | Records a payment. | | `identify(userId, traits)` | Tells Rectify who the visitor is. | | `optOut()` and `optIn()` | Stops or restarts analytics for this visitor. | ## init(projectId, userInfo, config) The install snippet passes the values from the object at its end: `projectId`, then `userInfo` and `config` if you add them. A second call on the same page is ignored, so a snippet pasted twice still shows one widget. ```js (function (w, d, s, o) { var js = d.createElement(s); js.src = o.widgetSrc; js.async = true; js.onload = function () { if (typeof w.Rectify === 'function') { w.RectifyInstance = new w.Rectify(); w.RectifyInstance.init(o.projectId, o.userInfo, o.config); } }; d.head.appendChild(js); }(window, document, 'script', { widgetSrc: 'https://api.rectify.so/widget/widget.umd.js', projectId: 'YOUR_PROJECT_ID', userInfo: { userId: 'user_123', email: 'jane@acme.com', name: 'Jane Doe', }, config: { initialTab: 'home', hideLauncher: false, }, })); ``` Copy the snippet from **Publish**, **Widget**, **Install** rather than from here. Rectify fills in your project ID there. ### userInfo Add `userInfo` only when someone is signed in to your site. | **Field** | **What it does** | | --- | --- | | `userId` or `id` | Your own ID for the user. Links their activity to one contact. | | `email` | Fills in forms and Support, and names the contact. | | `name` | Greets them by name and names the contact. | | `userHash` | A signature from your server that signs them in to the Roadmap, Changelog and Help tabs. See [Sign in verified users](/rectify/help/a/23-sign-in-verified-users). | Any other field you add, such as `plan` or `company`, is saved on the contact too. [Identify users and send events](/rectify/help/a/81-identify-users-and-send-events) lists the fields Rectify uses. ### config | **Option** | **Values** | **What it does** | | --- | --- | --- | | `initialTab` | `home`, `support`, `changelog`, `roadmap`, `help` | The tab the widget opens on. The default is `home`. | | `isOpen` | `true` or `false` | Opens the widget as soon as it loads. | | `hideLauncher` | `true` or `false` | Hides the launcher button. This overrides **Hide the launcher** in the widget settings. Open the widget from your own button with `control('open')`. | | `shortcuts` | An object | Keyboard shortcuts from your code. They replace the ones saved in Rectify. See Keyboard shortcuts below. | ## control(action, options) | **Call** | **What it does** | | --- | --- | | `control('open')` | Opens the widget. | | `control('open', { tab: 'changelog' })` | Opens the widget on a tab. | | `control('close')` | Closes the widget. | | `control('toggle')` | Opens it when closed and closes it when open. Also takes `{ tab }`. | | `control('switchTab', { tab: 'support' })` | Opens the widget on that tab. | | `control('openForm', { formType: 'bug' })` | Opens a form on the Home tab. | Tabs are `home`, `support`, `changelog`, `roadmap` and `help`. Use a tab that's turned on for your widget. Forms are `bug`, `idea`, `general` and `testimonial`. `openForm` does nothing if that form isn't on your widget's Home tab. Open the widget from your own button: ```js document.querySelector('#help-button').addEventListener('click', () => { window.RectifyInstance?.control('openForm', { formType: 'bug' }); }); ``` ![Controls and shortcuts, under Publish, Widget, Install.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106477630-01-controls.png) ## Keyboard shortcuts You can set shortcuts without code: under **Publish**, **Widget**, **Install**, turn on **Keyboard shortcuts** and fill in **Open**, **Close** and **Toggle**. The defaults are `ctrl+p`, `alt+x` and `ctrl+k`. From your code, pass a map of key combinations to actions. An action is `open`, `close` or `toggle`, or an object with `action` and `options` for the other actions. ```js config: { shortcuts: { 'ctrl+k': 'toggle', 'ctrl+b': { action: 'openForm', options: { formType: 'bug' } }, 'shift+h': { action: 'switchTab', options: { tab: 'help' } }, }, }, ``` `registerShortcuts()` takes the same map after the widget has started. It replaces every shortcut set before it. ```js window.RectifyInstance?.registerShortcuts({ 'ctrl+k': 'toggle', 'ctrl+b': { action: 'openForm', options: { formType: 'bug' } }, }); ``` How combinations work: - Join keys with `+`: `ctrl`, `alt` or `shift`, then one letter, number or character. `enter`, `escape`, `backspace` and `tab` work too. - `ctrl` also matches the Command key on a Mac. - Shortcuts don't fire while the visitor is typing in a field. - On a Mac, Option changes the character a key types, so `alt` shortcuts may not fire there. Prefer `ctrl` or `shift`. ## track(name, properties) Records a custom event for the current visitor. Use a short name in snake case, and keep the properties small. ```js window.RectifyInstance?.track('project_created', { template: 'blank', seats: 5 }); ``` - `name` is required. Names longer than 200 characters are cut. - `properties` is optional. Never put passwords, card numbers or tokens in it. - Events go out in batches, every 15 seconds, every 50 events, and when the visitor leaves the page. Custom events show on the contact's timeline, and you can use them in goals, segments and lead scoring. ## revenue(amount, currency, properties) Records a payment. Call it after a successful charge. ```js window.RectifyInstance?.revenue(49, 'USD', { plan: 'pro' }); ``` - `amount` must be a number. A string such as `'49'` is ignored. - `currency` defaults to `USD`. - It's saved as an event named `__revenue`, with the amount and currency in its properties. Revenue goals and the revenue alert use it. ## identify(userId, traits) Tells Rectify who the visitor is. Call it after sign-in or sign-up. ```js window.RectifyInstance?.identify('user_123', { email: 'jane@acme.com', name: 'Jane Doe', plan: 'pro', }); ``` If you pass no `userId`, Rectify uses `traits.email` instead. Calling it again with the same details on every page doesn't send anything new. [Identify users and send events](/rectify/help/a/81-identify-users-and-send-events) covers traits, companies and stages. ## optOut() and optIn() Wire these to your cookie or privacy banner. ```js window.RectifyInstance?.optOut(); window.RectifyInstance?.optIn(); ``` - `optOut()` stops analytics for this visitor straight away. Queued events are dropped and the saved identity is cleared. - `optIn()` turns analytics back on. - The choice is saved in the visitor's browser, so it holds on every page and visit. - The widget itself still shows and works after `optOut()`. ## Check it worked 1. Open your site and the browser console. 2. Run `window.RectifyInstance.control('open')`. The widget opens. 3. Run `window.RectifyInstance.track('test_event')`, wait 15 seconds, then open **Customers**, **Activity** in Rectify. The event shows there. ## Troubleshooting ### window.RectifyInstance is undefined The script hasn't loaded yet, or it isn't on this page. Use `window.RectifyInstance?.` in your calls, and see [The widget doesn't show on your site](/rectify/help/a/24-the-widget-does-not-show) if it never loads. ### control() logs "Widget not initialized" `init` hasn't run yet. Call `control` after the script's `onload`, or from a click handler. ### track() runs but no events arrive - Check that **Analytics Settings** shows **On**. Open **Customers**, **Analytics** and select the settings button at the top right. - Visitors whose browser sends Do Not Track are skipped while **Respect Do Not Track** is on, under **Capture**. - A visitor who opted out sends nothing until `optIn()` runs. - Your project may have reached its monthly event allowance. See [Compare plans](/rectify/help/a/13-compare-plans). ### "Invalid tab name" in the console `switchTab` only takes `home`, `support`, `changelog`, `roadmap` or `help`, in lowercase. ## Read next - [Identify users and send events](/rectify/help/a/81-identify-users-and-send-events) - [Send server events](/rectify/help/a/83-send-server-events) - [Install the Rectify widget on your site](/rectify/help/a/5-install-the-rectify-widget) --- # Identify users and send events Collection: Developers URL: https://app.rectify.so/rectify/help/a/81-identify-users-and-send-events Turn anonymous visitors into named contacts, attach their plan and company, and record the actions and payments that matter in your product. > **Note:** **Before you start.** The Rectify script must be on your site, and **Analytics** must be on for the project. Events count toward your plan's monthly analytics events, shown in [Compare plans](/rectify/help/a/13-compare-plans). The script records page views, clicks and other activity on its own. Two things need your code: telling Rectify who a visitor is, and recording the actions that matter in your product. Rectify then links the visitor's activity, feedback and chats to one contact under **Customers**, **Contacts**. ## Identify signed-in users Pick one of these. Both work the same way. ### In the script Add `userInfo` to the object at the end of your Rectify script when someone is signed in. Rectify identifies them on every page load. ```js userInfo: { userId: 'user_123', email: 'jane@acme.com', name: 'Jane Doe', }, ``` ### After sign-in Call `identify()` once your app knows who the user is, for example after sign-in or sign-up, or in your root layout when a session exists. ```js window.RectifyInstance?.identify(user.id, { email: user.email, name: user.name, plan: 'pro', }); ``` Rectify remembers the identity in the visitor's browser, so you don't need to call it on every page. Calling it again with the same details sends nothing new. ![Identify users and track revenue, in Setup guide under Customers, Contacts.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106480332-01-setup-guide.png) You'll find these snippets under **Customers**, **Contacts**, **Setup guide**, and under **Publish**, **Widget**, **Install**. ## What happens when you identify someone - Their earlier anonymous visits on that browser join their contact, so you see what they did before signing in. - Feedback and chats sent with the same email link to the contact. - Each trait is saved on its own. A later call without `plan` doesn't erase the plan you sent before. - If someone else already used that browser, the new person gets their own contact. - The first time a visitor becomes a contact, Rectify sends the **Visitor becomes a contact** event to your webhooks. See [Signed webhooks](/rectify/help/a/85-signed-webhooks). If you pass no user ID, Rectify uses the email as the ID. ## Traits Rectify uses You can send any traits you like. These ones drive contact stages, companies and revenue: | **Trait** | **What it does** | | --- | --- | | `email` | Names the contact and links their feedback and chats. | | `name` | The contact's display name. | | `plan` | Any plan other than `free` makes them a **Customer**. | | `mrr` | A value above 0 makes them a **Customer**. | | `status` | `churned`, `canceled` or `cancelled` makes them **Churned**. | | `company` | Groups contacts into a company. See below. | Every contact has one stage, worked out in this order: | **Stage** | **When** | | --- | --- | | **Churned** | `status` is `churned`, `canceled` or `cancelled`, or `churned` is `true` | | **Customer** | `mrr` is above 0, or `plan` is set and isn't `free` | | **User** | You passed a user ID | | **Lead** | Rectify knows their email | | **Visitor** | Anyone else | Rectify also reads `plan`, `mrr` and `status` from `company` when the contact has none of their own. ## Group contacts into companies Send a `company` object to group people from the same account: ```js window.RectifyInstance?.identify(user.id, { email: user.email, company: { id: 'acct_42', name: 'Acme', domain: 'acme.com', plan: 'pro', mrr: 490, seats: 20, }, }); ``` - `company.id` is your own account ID. It's the most reliable way to group people. - Without an ID, Rectify groups by `company.domain`, then by the domain of the person's work email. Personal email providers such as Gmail and Outlook are never grouped. - `mrr`, `seats` and `plan` show on the company under **Customers**, **Contacts**, **Companies**. ## Record actions with track() Track three to five actions that show someone is getting value, such as a project created or a report exported. Page views, clicks, form submissions, errors, downloads, outbound links and site searches are already recorded, so don't track those yourself. ```js window.RectifyInstance?.track('project_created', { template: 'blank' }); ``` Use the same name every time for the same action. Custom events show on the contact's timeline, and you can build goals, segments and lead scoring on them. ## Record payments with revenue() ```js window.RectifyInstance?.revenue(49, 'USD', { plan: 'pro' }); ``` The amount must be a number. The currency defaults to `USD`. Revenue goals and the **Revenue** alert use these payments. ## Keep sensitive things out Form field values are never sent, only field names and whether each one was filled. For anything else, mark your HTML: ```html
Nothing in here produces an event.
Events still fire, but text and values are dropped.
``` `data-rectify-capture-value` opts a single field's value in. It never works for card numbers, security codes and similar fields. Never put passwords, card numbers or tokens in traits or event properties. ## Check it worked 1. Sign in to your own site. 2. In Rectify, open **Customers**, **Contacts**. Your contact shows with your name and email. 3. Open the contact. Your page views, and any custom events, show on the timeline. ## Troubleshooting ### The contact never gets a name or email Rectify only accepts identity from your own site. If your project has a website address, `identify()` and `userInfo` count only on that domain, its subdomains and `localhost`. Check that your project's website address matches your live site. ### Nothing arrives at all - Check **Analytics Settings** shows **On**. Open **Customers**, **Analytics** and select the settings button at the top right. - Browsers that send Do Not Track are skipped while **Respect Do Not Track** is on, under **Capture**. - A visitor who opted out with `optOut()` sends nothing until `optIn()` runs. ### Two people share one computer When a second person signs in on the same browser, call `identify()` with their details. Rectify gives them their own contact instead of overwriting the first one. ## Read next - [Widget JavaScript API reference](/rectify/help/a/80-widget-javascript-api-reference) - [Contacts API](/rectify/help/a/82-contacts-api) - [Send server events](/rectify/help/a/83-send-server-events) --- # Contacts API Collection: Developers URL: https://app.rectify.so/rectify/help/a/82-contacts-api Create and update contacts from your server, backfill up to 500 at a time, and attach your own records such as subscriptions or orders. > **Note:** **Before you start.** You need your project's write key and access to your server's code. **Analytics** must be on for the project. Custom objects need a paid plan: Build allows 2 per project, Launch 5, Accelerate 20 and Enterprise has no limit. Use the Contacts API to keep contacts up to date from your backend, even when people don't open your app. Plan changes, revenue and account details you send here show on the contact and their company under **Customers**, **Contacts**. ## Base URL and authentication ```text https://api.rectify.so/v1/contacts ``` Send your write key as a bearer token, and send JSON: ```text Authorization: Bearer YOUR_WRITE_KEY Content-Type: application/json ``` To find the write key: 1. Open **Customers**, then **Analytics**. 2. Select the settings button at the top right. 3. Under **Setup**, copy the **Write Key**. **Customers**, **Contacts**, **Setup guide** also shows these calls with your write key filled in. Keep the key in an environment variable on your server, not in your code. ![Sync from your backend, in the Contacts setup guide. The write key is hidden here.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106483154-01-sync-from-backend.png) ## Endpoints | **Method** | **Path** | **What it does** | | --- | --- | --- | | `POST` | `/v1/contacts/identify` | Creates or updates one contact. | | `POST` | `/v1/contacts/bulk` | Creates or updates up to 500 contacts. | | `POST` | `/v1/contacts/objects/{objectKey}` | Creates or updates one custom object record. | | `POST` | `/v1/contacts/objects/{objectKey}/bulk` | Creates or updates up to 500 records. | | `DELETE` | `/v1/contacts/objects/{objectKey}/{externalId}` | Deletes one record. | ## Create or update a contact `POST /v1/contacts/identify` | **Field** | **Type** | **Notes** | | --- | --- | --- | | `userId` | string | Your own ID for the person. | | `email` | string | Saved in lowercase. | | `name` | string | Optional. | | `company` | object | Optional. `id`, `name`, `domain`, `plan`, `mrr`, `seats` and `status` group the person into a company. | | `attributes` | object | Optional. Any other traits, such as `plan`, `mrr` or `status`. | Send `userId`, `email` or both. Rectify looks for an existing contact by `userId` first, then by `email`, and creates one if neither matches. Each attribute is saved on its own, so fields you leave out keep their values. **curl** ```bash curl -X POST https://api.rectify.so/v1/contacts/identify \ -H "Authorization: Bearer $RECTIFY_WRITE_KEY" \ -H "Content-Type: application/json" \ -d '{ "userId": "user_123", "email": "jane@acme.com", "name": "Jane Doe", "company": { "id": "acct_42", "name": "Acme", "plan": "pro", "mrr": 490 }, "attributes": { "plan": "pro", "role": "admin" } }' ``` **Node.js** ```js const response = await fetch('https://api.rectify.so/v1/contacts/identify', { method: 'POST', headers: { Authorization: `Bearer ${process.env.RECTIFY_WRITE_KEY}`, 'Content-Type': 'application/json', }, body: JSON.stringify({ userId: 'user_123', email: 'jane@acme.com', name: 'Jane Doe', company: { id: 'acct_42', name: 'Acme', plan: 'pro', mrr: 490 }, attributes: { plan: 'pro', role: 'admin' }, }), }); console.log(await response.json()); ``` The response: ```json { "ok": true, "contact": { "visitorId": "srv_6f1c2a90-3b1e-4d0a-9a51-2f7c8e4b1d33", "userId": "user_123", "email": "jane@acme.com", "name": "Jane Doe" } } ``` The `plan`, `mrr` and `status` attributes set the contact's stage, the same as traits sent from the browser. [Identify users and send events](/rectify/help/a/81-identify-users-and-send-events) explains stages and companies. ## Backfill many contacts `POST /v1/contacts/bulk` takes a `contacts` array of 1 to 500 items. Each item has the same fields as `/identify`. ```bash curl -X POST https://api.rectify.so/v1/contacts/bulk \ -H "Authorization: Bearer $RECTIFY_WRITE_KEY" \ -H "Content-Type: application/json" \ -d '{ "contacts": [ { "userId": "user_123", "email": "jane@acme.com", "attributes": { "plan": "pro" } }, { "email": "sam@acme.com", "name": "Sam Lee" } ] }' ``` ```json { "ok": true, "processed": 2, "failed": 0 } ``` An item with neither `userId` nor `email` counts as `failed`. The others are still saved. ## Attach your own records Custom objects put records from your own database on a contact or company: subscriptions, orders, tickets, anything. Each field you define becomes something you can filter segments by. ### Define the object 1. Open **Customers**, then **Contacts**, and select the **Objects** tab. 2. Select **Let's GO!**, or **New Object** if you already have one. 3. Enter a **Name**, such as Subscription, and its **Plural**. 4. Add a row under **Fields** for each field. Pick its **Type**: **Text**, **Number**, **Yes / no**, **Date** or **One of a list**. Turn on **Required** for fields every record must have. 5. Select **Create**. ![Create Custom Object, under Customers, Contacts, Objects.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106485033-02-create-object.png) The object's key is its name in lowercase, with underscores for spaces: Subscription becomes `subscription`. Field keys are made the same way from their labels, so Renews on becomes `renews_on`. The key shows next to the object's name in the **Objects** list. An object can have up to 50 fields. ### Send records `POST /v1/contacts/objects/{objectKey}` | **Field** | **Type** | **Notes** | | --- | --- | --- | | `externalId` | string | Required. Your own ID for the record. `id` works too. | | `userId` or `email` | string | The person the record belongs to. | | `companyId` or `companyDomain` | string | The company it belongs to, when it isn't a person's. | | `data` | object | The record's fields, by field key. | ```bash curl -X POST https://api.rectify.so/v1/contacts/objects/subscription \ -H "Authorization: Bearer $RECTIFY_WRITE_KEY" \ -H "Content-Type: application/json" \ -d '{ "externalId": "sub_123", "email": "jane@acme.com", "data": { "plan": "pro", "seats": 20, "renews_on": "2026-12-01" } }' ``` ```json { "ok": true, "contactLinked": true, "companyLinked": true } ``` How records are saved: - Sending the same `externalId` again updates that record instead of making a second one. - Each write replaces the record's `data`, so send every field each time. - Values are checked against the field type. Numbers must be numbers, dates must be valid dates, and **One of a list** values must match an option. Text is cut at 2,000 characters. - Fields you didn't define are dropped. - A record that belongs to a person also counts for their company. If you name an owner and Rectify can't find them, the record is still saved, but it isn't attached to anyone. The response then includes a `warning`. Identify the contact first, then send the record again. ### Backfill and delete records `POST /v1/contacts/objects/{objectKey}/bulk` takes a `records` array of 1 to 500 items, each shaped like a single record. ```json { "ok": true, "processed": 499, "failed": 1, "failures": [{ "index": 12, "error": "Field \"seats\" must be a number" }] } ``` One bad record doesn't stop the rest. `failures` lists up to 20 of them, by position in your array. To delete a record: ```bash curl -X DELETE https://api.rectify.so/v1/contacts/objects/subscription/sub_123 \ -H "Authorization: Bearer $RECTIFY_WRITE_KEY" ``` ```json { "ok": true, "deleted": 1 } ``` ## Errors and limits Errors come back as JSON with an `error` message, for example `{ "error": "userId or email is required" }`. | **Status** | **When** | | --- | --- | | `400` | A required field is missing, a value doesn't fit the field type, or an array has more than 500 items. | | `401` | The write key is missing or wrong. The key the Rectify script uses on your site doesn't work here. | | `403` | **Analytics** is off for the project. | | `404` | No custom object with that key exists in the project. | | `429` | Too many requests. Wait a minute and try again. | Each IP address can make up to 120 Contacts API requests a minute. Across the whole API, each IP address can also make up to 500 requests every 15 minutes. Use the bulk endpoints for large imports. ## Get a new write key If the key gets out, open the **Write Key** under **Analytics Settings** and select the regenerate button next to it. Only Owners and Admins can do this. Your old key stops working at once, so update your server straight away. The Rectify script on your site uses a different key, so it keeps working. ## Check it worked Open **Customers**, then **Contacts**, and search for the email you sent. The contact shows your name, stage and company. Records you sent show on the contact's profile. ## Troubleshooting ### I get 403 "Analytics is disabled for this project" Open **Customers**, **Analytics**, select the settings button and turn the switch **On**. ### My record came back with a warning No contact or company matched the `userId`, `email`, `companyId` or `companyDomain` you sent. Send the contact with `/v1/contacts/identify` first, then send the record again with the same `externalId`. ### I get 404 Custom object is not defined Check the object key in the path. It's lowercase with underscores, and shows next to the object's name under **Objects**. ## Read next - [Identify users and send events](/rectify/help/a/81-identify-users-and-send-events) - [Send server events](/rectify/help/a/83-send-server-events) - [Signed webhooks](/rectify/help/a/85-signed-webhooks) --- # Send server events Collection: Developers URL: https://app.rectify.so/rectify/help/a/83-send-server-events Record signups, payments and other events from your backend, and see them on the right contact next to what they did in the browser. > **Note:** **Before you start.** You need your project's write key and access to your server's code. **Analytics** must be on for the project. Server events count toward your plan's monthly analytics events, shown in [Compare plans](/rectify/help/a/13-compare-plans). Some events only your server knows about for sure: a payment that cleared, a renewal, a plan change from your billing system. Send them to the same place the Rectify script sends browser events, and they show up in your analytics and on the contact's timeline. ## Get your write key 1. Open **Customers**, then **Analytics**. 2. Select the settings button at the top right. 3. Under **Setup**, copy the **Write Key**. ![3 Copy the Write Key, under Analytics Settings, Setup. The key is hidden here.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106487541-01-server-api.png) Keep the key in an environment variable on your server, such as `RECTIFY_WRITE_KEY`. ## The request `POST https://api.rectify.so/v1/analytics/ingest` | **Header** | **Value** | | --- | --- | | `Authorization` | `Bearer YOUR_WRITE_KEY` | | `Content-Type` | `application/json` | The body holds one visitor, one session and up to 100 events: | **Field** | **Type** | **Notes** | | --- | --- | --- | | `visitorId` | string | Required. 1 to 128 characters. Can't start with `pv_` or `portal_`. | | `sessionId` | string | Required. 1 to 128 characters. | | `events` | array | Required. 1 to 100 events. | Each event: | **Field** | **Type** | **Notes** | | --- | --- | --- | | `type` | string | Use `custom` for your own events. | | `name` | string | The event name, up to 200 characters. | | `timestamp` | number | Required. When it happened, in milliseconds since 1970 (`Date.now()`). | | `userId` | string | Your own ID for the person. Shows the event on their contact. | | `properties` | object | Optional details, such as `{ "plan": "pro" }`. | ## Send an event Send `userId` on each event so it lands on the right contact. For `visitorId`, use the contact's `visitorId`. The [Contacts API](/rectify/help/a/82-contacts-api) returns it when you identify the person, and identifying first also makes sure the contact exists. **curl** ```bash curl -X POST https://api.rectify.so/v1/analytics/ingest \ -H "Authorization: Bearer $RECTIFY_WRITE_KEY" \ -H "Content-Type: application/json" \ -d '{ "visitorId": "srv_6f1c2a90-3b1e-4d0a-9a51-2f7c8e4b1d33", "sessionId": "billing-server", "events": [{ "type": "custom", "name": "plan_upgraded", "userId": "user_123", "timestamp": 1793091600000, "properties": { "from": "free", "to": "pro" } }] }' ``` **Node.js** ```js const headers = { Authorization: `Bearer ${process.env.RECTIFY_WRITE_KEY}`, 'Content-Type': 'application/json', }; const identify = await fetch('https://api.rectify.so/v1/contacts/identify', { method: 'POST', headers, body: JSON.stringify({ userId: user.id, email: user.email }), }); const { contact } = await identify.json(); const response = await fetch('https://api.rectify.so/v1/analytics/ingest', { method: 'POST', headers, body: JSON.stringify({ visitorId: contact.visitorId, sessionId: 'billing-server', events: [{ type: 'custom', name: 'plan_upgraded', userId: user.id, timestamp: Date.now(), properties: { from: 'free', to: 'pro' }, }], }), }); console.log(await response.json()); ``` A saved batch returns: ```json { "ok": true, "accepted": 1 } ``` `accepted` is the number of events stored. Use one `sessionId` per job or process, such as `billing-server`. A new `visitorId` that Rectify hasn't seen before creates a new anonymous contact, which is why the contact's own `visitorId` works best. ## Send a payment Name the event `revenue` and put the amount, as a number, in `properties.amount`. The currency defaults to `USD`. ```json { "type": "custom", "name": "revenue", "userId": "user_123", "timestamp": 1793091600000, "properties": { "amount": 49, "currency": "USD", "plan": "pro" } } ``` Revenue goals and the **Revenue** alert count these payments, the same as `revenue()` in the browser. ## Who the event belongs to - The `userId` on an event shows it on the contact with that user ID, next to their browser activity. - Sending an event doesn't change a contact's name, email, plan or company. Use `POST /v1/contacts/identify` from the [Contacts API](/rectify/help/a/82-contacts-api) for that. - `identify` events sent here from a server are stored, but they don't update the contact when your project has a website address. Rectify only takes identity from your own site. ## Errors and limits | **Status** | **Body** | **What to do** | | --- | --- | --- | | `400` | `{ "error": "..." }` | A field is missing or the wrong type. Check `visitorId`, `sessionId`, `events` and each `timestamp`. | | `401` | `{ "error": "Invalid analytics write key" }` | Copy the write key again. | | `403` | `{ "error": "Analytics is disabled for this project" }` | Turn **Analytics Settings** **On**. | | `429` | `{ "ok": false, "error": "Monthly event quota exceeded", "used": ..., "limit": ... }` | Your plan's monthly events are used up. Upgrade or wait for next month. | | `429` | `{ "error": "Too many ingest requests, please slow down" }` | Wait a minute and retry. | Each write key can send up to 120 requests a minute, and each IP address up to 500 requests to the API every 15 minutes. Put up to 100 events in one request instead of sending them one by one. ## Check it worked 1. Send a test event with your own user ID. 2. Open **Customers**, **Contacts**, then your contact. The event shows on the timeline. 3. Or open **Customers**, **Activity** and look for the event name. ## Troubleshooting ### The event doesn't show on the contact Check that the event's `userId` matches the user ID on the contact exactly. If the contact has no user ID, identify it first with the Contacts API. ### I see new anonymous contacts after sending events Each new `visitorId` creates a visitor. Use the `visitorId` the Contacts API returns for the person instead of making one up. ## Read next - [Contacts API](/rectify/help/a/82-contacts-api) - [Identify users and send events](/rectify/help/a/81-identify-users-and-send-events) - [Widget JavaScript API reference](/rectify/help/a/80-widget-javascript-api-reference) --- # Transactional email API Collection: Developers URL: https://app.rectify.so/rectify/help/a/84-transactional-email-api Send receipts, password resets and other product emails from your server with a secret server key, and retry safely without sending twice. > **Note:** **Before you start.** Only Owners and Admins can create, rotate or revoke the server key. You need access to your server's code to send. Your backend sends an email with one request. Rectify checks the address against your suppression list, sends it, and logs it under **Customers**, **Messaging**, **Log**. ## Create a server key 1. Open **Customers**, then **Messaging**, and select the **API** tab. 2. Select **Let's GO!**. ![1 API tab. 2 Let's GO!, to create the project's server key.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106490342-01-api-tab.png) 3. Copy the key from **Copy your server key** and store it on your server, for example as `RECTIFY_SERVER_KEY`. Then select **Done**. ![Copy your server key. The key is hidden here.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106492076-02-copy-key.png) The key starts with `rsk_` and is shown only this once. Rectify keeps only a fingerprint of it, so nobody can see it again, including you. Each project has one server key. > **Warning:** Keep the server key on your server. Never put it in your site's code or a mobile app. The analytics write key and the key the Rectify script uses can't send email. ## Send an email `POST https://api.rectify.so/v1/messages/transactional` | **Header** | **Value** | | --- | --- | | `Authorization` | `Bearer YOUR_SERVER_KEY` | | `Content-Type` | `application/json` | | `Idempotency-Key` | Optional. Your own ID for this email, up to 200 characters. | | **Field** | **Type** | **Notes** | | --- | --- | --- | | `to` | string | Required. One email address. | | `subject` | string | Required. Cut at 300 characters. | | `html` | string | Required. The email body as HTML, up to 512 KB. | | `category` | string | `transactional` (the default), `product` or `marketing`. See below. | | `templateKey` | string | Optional. Your own label for the kind of email, such as `receipt`, up to 100 characters. | | `idempotencyKey` | string | Optional. The same as the header, for clients that can't set headers. | | `experimentId` | string | Optional. The ID of an experiment from the **Experiments** tab. | **curl** ```bash curl -X POST https://api.rectify.so/v1/messages/transactional \ -H "Authorization: Bearer $RECTIFY_SERVER_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: order-1042-receipt" \ -d '{ "to": "jane@example.com", "subject": "Your receipt for order 1042", "html": "

Thanks for your order, Jane.

", "templateKey": "receipt" }' ``` **Node.js** ```js const response = await fetch('https://api.rectify.so/v1/messages/transactional', { method: 'POST', headers: { Authorization: `Bearer ${process.env.RECTIFY_SERVER_KEY}`, 'Content-Type': 'application/json', 'Idempotency-Key': `order-${order.id}-receipt`, }, body: JSON.stringify({ to: order.email, subject: `Your receipt for order ${order.id}`, html: '

Thanks for your order.

', templateKey: 'receipt', }), }); const result = await response.json(); ``` ![The server key and the send example, under Messaging, API.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106493522-03-key-row.png) ## Responses A sent email returns `200`: ```json { "messageId": "6a1f2c3d4e5f6a7b8c9d0e1f", "status": "sent", "deduplicated": false } ``` When Rectify accepts the request but doesn't send the email, it returns `202` with a `reason`: ```json { "messageId": "6a1f2c3d4e5f6a7b8c9d0e20", "status": "suppressed", "deduplicated": false, "reason": "suppressed:hard_bounce" } ``` | **status** | **What happened** | | --- | --- | | `sent` | The email went out. | | `suppressed` | Rectify held it back. `reason` says why. | | `failed` | The send failed. `reason` has the error. | Common reasons: | **reason** | **Meaning** | | --- | --- | | `suppressed:hard_bounce`, `suppressed:complaint`, `suppressed:unsubscribe`, `suppressed:manual` or `suppressed:invalid` | The address is on your project's suppression list. See **Messaging**, **Suppressions**. | | `suppressed:global` | The address is blocked on Rectify's own sending list. | | `unsubscribed:marketing` or `unsubscribed:product` | The person unsubscribed from that kind of email. | | `frequency_capped` | The person already got 3 product or marketing emails in the last 24 hours. | | `holdout` | The person is in the experiment's holdout group. | ## Send it once, even when you retry Give each email an `Idempotency-Key` that's unique to it, such as `order-1042-receipt`. If you send the same key again, Rectify doesn't send a second email. It returns the first one's `messageId` and status, with `"deduplicated": true`. That makes it safe to retry after a timeout or a network error. Keys are per project. Don't reuse one for a different email. ## Categories | **category** | **Use it for** | **What Rectify adds** | | --- | --- | --- | | `transactional` | Receipts, password resets, sign-in codes | Nothing. No consent check, no daily cap, no unsubscribe link. | | `product` | Product updates and tips | An unsubscribe link and header. Skips people who unsubscribed. At most 3 product or marketing emails a day per person. | | `marketing` | Promotions | The same as `product`, checked against marketing unsubscribes. | A value Rectify doesn't recognise is treated as `transactional`. ## Who it comes from By default, emails come from `Rectify `. To send from your own domain: 1. Connect Resend under **Project settings**, **Integrations**. 2. Open **Project settings**, **Email notifications**, and turn on **Project emails** under **Sending domain**. Emails sent through your own domain have no delivery tracking. They stay marked **Sent** in the **Log**, without **Delivered** or **Bounced**. ## Rotate or revoke the key Both are on the **API** tab, next to the key. - **Rotate** makes a new key and shows it once. The old key stops working straight away, so update your server first. - **Revoke** deletes the key. Emails from your server fail until you create a new one. ## Errors and limits | **Status** | **error** | **Fix** | | --- | --- | --- | | `400` | Names the field, for example `to A valid email is required` | Fix the field and send again. | | `401` | `Server key required. Send it as Authorization: Bearer ` | Add the header. | | `401` | `This endpoint needs your secret server key from Messaging > API. The public write key cannot send email` | You sent the write key. Use the server key. | | `401` | `Invalid server key` | The key was rotated or revoked. Use the current one. | | `429` | `Too many send requests, please slow down` | Wait a minute, then retry with the same `Idempotency-Key`. | Each server key can send up to 300 requests a minute. Each IP address can also make up to 500 requests to the API every 15 minutes. ## Check it worked Send an email to your own address. Then open **Customers**, **Messaging**, **Log** and filter by your address. The email shows with its status, and the key shows **Last used** on the **API** tab. ## Troubleshooting ### The response is 202 and no email arrived Read `status` and `reason` in the response. A suppressed address stays blocked until you remove it under **Messaging**, **Suppressions**. Only Owners and Admins can remove one. ### I sent the same email twice by mistake Use an `Idempotency-Key` that's unique to each email. Retries with that key never send a second time. ### The email came from Rectify, not my domain Check that Resend is connected under **Integrations** and that **Project emails** is on under **Email notifications**, **Sending domain**. ## Read next - [Contacts API](/rectify/help/a/82-contacts-api) - [Signed webhooks](/rectify/help/a/85-signed-webhooks) - [Roles and project access: Owner, Admin and Member](/rectify/help/a/9-roles-and-project-access) --- # Signed webhooks Collection: Developers URL: https://app.rectify.so/rectify/help/a/85-signed-webhooks Send Rectify events to your own server, check each request's signature, and handle retries, tests and secret rotation. > **Note:** **Before you start.** Owners, Admins and Members can add, test, pause and rotate endpoints, and see their deliveries. Only Owners and Admins can delete one. You need a public HTTPS address that accepts `POST` requests. A webhook endpoint gets a `POST` request from Rectify each time an event you picked happens, such as new feedback or a contact entering a segment. Every request is signed, so your server can check it came from Rectify. ## Add an endpoint 1. Open **Project settings**, then **Automation**. 2. Select the **Webhooks** tab. 3. Select **Let's GO!**, or **Add Endpoint** if you already have one. ![2 Webhooks tab. 3 Let's GO!](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106496115-01-webhooks-tab.png) 4. Enter the **URL** of your endpoint. 5. Add a **Description** if you like, up to 200 characters. 6. Under **Events**, pick the events to send. Leave them all unchecked to get every event, including ones Rectify adds later. ![4 URL. 5 Description. 6 Events.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106497543-02-add-endpoint.png) 7. Select **Create endpoint**. 8. Copy the secret from **Save your signing secret** and store it on your server. Then select **I have saved it**. The signing secret starts with `whsec_` and is shown only this once. A project can have up to 10 endpoints. ## Events | **Event type** | **Shown as** | **data**** fields** | | --- | --- | --- | | `feedback.created` | New feedback submitted | `feedbackId`, `type`, `title`, `priority`, `status`, `pageUrl`, `reporter` (`name`, `email`), `url` | | `feedback.status_changed` | Feedback status changed | `feedbackId`, `title`, `type`, `priority`, `fromStatus`, `toStatus` | | `feedback.assigned` | Feedback assigned | `feedbackId`, `title`, `type`, `priority`, `assigneeId`, `assigneeEmail` | | `contact.identified` | Visitor becomes a contact | `contactId`, `visitorId`, `userId`, `email`, `name`, `traits` | | `segment.entered` | Contact enters a segment | `segmentId`, `segmentName`, `contactId`, `visitorId` | | `segment.exited` | Contact leaves a segment | `segmentId`, `segmentName`, `contactId`, `visitorId` | | `score.threshold_crossed` | Lead score crosses a band | `contactId`, `visitorId`, `score`, `previousScore`, `band`, `previousBand`, `direction` (`up` or `down`) | | `form.submitted` | Form submitted | `contactId`, `email`, `name`, `visitorId`, `pageUrl`, `formName`, `fieldCount`, `fields` | | `survey.answered` | Survey answered | `surveyId`, `surveyName`, `responseId`, `contactId`, `visitorId` | | `help.article_published` | Help article published | `article` (`id`, `title`, `description`, `url`, `collection`, `locale`, `publishedAt`) | | `help.article_feedback` | Help article rated | `article` (`id`, `title`, `url`), `helpful`, `reason`, `source`, `locale` | | `help.search_no_results` | Help search found nothing | `query`, `normalized`, `searches`, `locale`, `source` | A few details: - `contact.identified` fires once, the first time a visitor is identified. - `form.submitted` covers forms on your own site, not the widget's forms. It never includes what people typed. - `help.search_no_results` fires at most once a day for the same search. ## What Rectify sends Each delivery is a `POST` with a JSON body: ```json { "id": "evt_6a1f2c3d4e5f6a7b8c9d0e1f", "type": "feedback.created", "occurredAt": "2026-10-27T09:15:00.000Z", "projectId": "6addf8c8f1748a2b2950c3f4", "data": { "feedbackId": "6a1f2c3d4e5f6a7b8c9d0e20", "type": "bug", "title": "Export button does nothing", "priority": "high", "status": "open", "pageUrl": "https://acme.example/reports", "reporter": { "name": "Jane Doe", "email": "jane@example.com" }, "url": "https://app.rectify.so/projects/acme-app/feedback/6a1f2c3d4e5f6a7b8c9d0e20" } } ``` The headers: | **Header** | **Value** | | --- | --- | | `Content-Type` | `application/json` | | `User-Agent` | `Rectify-Webhooks/1.0` | | `X-Rectify-Event` | The event type, such as `feedback.created` | | `X-Rectify-Delivery` | The delivery ID. It stays the same when Rectify retries. | | `X-Rectify-Timestamp` | When this attempt was sent, in milliseconds since 1970 | | `X-Rectify-Signature` | The signature, as 64 hexadecimal characters | `id` is the same for every endpoint that gets the event. Use it, or `X-Rectify-Delivery`, to skip events you've already handled. ## Check the signature The signature is an HMAC-SHA256 of the timestamp, a full stop and the raw request body, with your whole signing secret as the key, written in hexadecimal: ```text HMAC_SHA256(secret, X-Rectify-Timestamp + "." + raw_body) ``` Check it against the raw body exactly as it arrived, before you parse the JSON. **Node.js** ```js import crypto from 'node:crypto'; import express from 'express'; const app = express(); app.post('/hooks/rectify', express.raw({ type: 'application/json' }), (req, res) => { const timestamp = req.get('X-Rectify-Timestamp') ?? ''; const signature = req.get('X-Rectify-Signature') ?? ''; const expected = crypto .createHmac('sha256', process.env.RECTIFY_WEBHOOK_SECRET) .update(`${timestamp}.${req.body.toString('utf8')}`) .digest('hex'); const valid = signature.length === expected.length && crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected)); const fresh = Math.abs(Date.now() - Number(timestamp)) < 5 * 60 * 1000; if (!valid || !fresh) return res.status(401).end(); const event = JSON.parse(req.body.toString('utf8')); res.status(200).end(); handleEvent(event); }); ``` **Python** ```python import hashlib import hmac import json import os import time from flask import Flask, request app = Flask(__name__) @app.post("/hooks/rectify") def rectify_webhook(): timestamp = request.headers.get("X-Rectify-Timestamp", "") signature = request.headers.get("X-Rectify-Signature", "") body = request.get_data() expected = hmac.new( os.environ["RECTIFY_WEBHOOK_SECRET"].encode(), timestamp.encode() + b"." + body, hashlib.sha256, ).hexdigest() fresh = timestamp.isdigit() and abs(time.time() * 1000 - int(timestamp)) < 5 * 60 * 1000 if not hmac.compare_digest(signature, expected) or not fresh: return "", 401 event = json.loads(body) handle_event(event) return "", 200 ``` The five-minute check on the timestamp is up to you. It stops someone replaying an old request. Rectify sends a fresh timestamp and signature on every attempt, so retries pass it. ## Retries and failures - Rectify waits up to 10 seconds for an answer. Any `2xx` status counts as delivered. - Redirects aren't followed, so a `3xx` counts as a failure. - A failed delivery is tried again, up to 5 attempts in total, with longer waits between them, starting at about 10 seconds. - If your endpoint answers with an error 20 times in a row, Rectify turns it off and shows **Paused** on it. Rectify doesn't email you about this. Fix your endpoint, then turn its switch back on. - Events that happen while an endpoint is off aren't sent later. Answer with a `2xx` as soon as you've checked the signature, and do the slow work afterwards. ## Test an endpoint Select **Send a test event** on the endpoint. Rectify sends a sample of the first event the endpoint listens to, or of **Contact enters a segment** if it listens to everything. The test is signed like a real delivery. Its `id` is `evt_test`, it has `"test": true`, and its `data` holds sample values. ## See deliveries Each endpoint lists its recent deliveries: the status code, the event type, the number of attempts, how long it took and when. Rectify keeps deliveries for 14 days. ## Rotate the signing secret Select **Rotate the signing secret** on the endpoint. Rectify shows the new secret once, in **Save your signing secret**. The old secret stops working at once, and retries still waiting are signed with the new one. Update your server straight away. ## Pause, change or delete an endpoint - Use the switch on the endpoint to pause it or turn it back on. - To change the URL or the events, delete the endpoint and add it again. - To delete, select the delete button, then **Delete**. Deliveries stop straight away. ## URL rules - The URL must use HTTPS. - Private and internal addresses, such as `localhost` or `10.0.0.1`, are rejected. So are addresses that resolve to them. - Usernames and passwords in the URL aren't allowed. - Ports 22, 23, 25, 445, 3306, 5432, 6379, 9200, 11211 and 27017 are blocked. The **Webhook** integration on the **Integrations** page is a separate, simpler feature. Its requests aren't signed and aren't retried. ## Check it worked 1. Select **Send a test event** on your endpoint. 2. Check that your server logged the request and that the signature matched. 3. The delivery shows on the endpoint with a `2xx` status. ## Troubleshooting ### The signature never matches - Sign the raw body exactly as it arrived. Parsing and re-encoding the JSON changes it. - Use the whole secret, including `whsec_`, as the key. - Put a full stop between the timestamp and the body. - If you rotated the secret, update your server with the new one. ### My endpoint shows Paused It returned an error 20 times in a row. Fix it, then turn its switch back on. ### I get "Webhook URLs must use HTTPS" or "That address is not reachable from webhooks" Use a public HTTPS address. To test on your own computer, put it behind a public HTTPS tunnel. ### I get "At most 10 endpoints per project" Delete an endpoint you no longer use, or send several event types to one endpoint. ## Read next - [Contacts API](/rectify/help/a/82-contacts-api) - [Identify users and send events](/rectify/help/a/81-identify-users-and-send-events) - [Roles and project access: Owner, Admin and Member](/rectify/help/a/9-roles-and-project-access) --- # Connect an AI app to Rectify over MCP Collection: Developers URL: https://app.rectify.so/rectify/help/a/86-connect-an-ai-app-to-rectify-over-mcp Let Claude, ChatGPT, Cursor, VS Code and other AI apps read and update your Rectify project through the hosted MCP server. > **Note:** **Before you start.** The MCP server needs the Build plan or higher. Anyone on your team can connect an app. The app works as you, with your role, in the project you pick. MCP is the standard way AI apps use outside tools. Once connected, your AI app can work on your feedback, roadmap, changelog, help center, inbox, monitoring, contacts, analytics and more, with 142 tools across 23 areas. Every app connects to the same hosted server: ```text https://api.rectify.so/v1/mcp ``` ## Two ways to connect - **Sign in with Rectify.** Claude, ChatGPT, Claude Desktop, Cursor, VS Code, Kiro and Antigravity open Rectify in your browser. You pick the project and approve, and no key is needed. - **Use a key.** Claude Code, Windsurf and other MCP clients send an MCP key in a header. Create one first, as [Manage MCP keys and connected apps](/rectify/help/a/87-manage-mcp-keys-and-connected-apps) shows. ## Connect an app 1. In your project, open **Project settings**, then **MCP server**. 2. Under **Connect an app**, select your app. ![The apps under Connect an app, on the MCP Server page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106500451-01-connect-an-app.png) 3. Follow the steps in the panel that opens. They're written for that app, and the next sections repeat them. ![Connect Claude, with the server URL to paste.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106501873-02-claude-sheet.png) The panel also lists what the app can do, by area. Hover an area to see its tools. ## Approve the connection Apps that sign in send you to a Rectify page called **Connect** with the app's name. 1. Check you're signed in as the right person. If not, select **Switch account**. 2. Pick the **Organization**, if you belong to more than one, and the **Project**. 3. Check the note that says where Rectify sends you back. For an app Rectify doesn't recognise, it adds **Only connect apps you trust.** 4. Select **Connect** with the app's name, for example **Connect Claude**. Rectify sends you back to the app. Select **Cancel** to stop instead. The link from your app works for 15 minutes. If it expires, start again from the app. ## Claude and Claude Desktop 1. In Claude, open **Settings**, then **Connectors**, and select **Add custom connector**. 2. Name it Rectify and paste `https://api.rectify.so/v1/mcp` as the URL. Leave the OAuth client ID empty. 3. Select **Connect**, pick the project in your browser and select **Connect Claude**. 4. In a chat, open the **+** menu under the message box and turn on Rectify. A connector added on claude.ai also shows in Claude Desktop. ## ChatGPT 1. Open **Settings**, **Connectors**, **Advanced** and turn on **Developer mode**. 2. Select **Create**. Name it Rectify, paste `https://api.rectify.so/v1/mcp` and choose OAuth. 3. Pick the project in your browser and select **Connect ChatGPT**. 4. In a chat, turn it on under **Tools**. ## Cursor, VS Code and Kiro Select **Add to Cursor**, **Add to VS Code** or **Add to Kiro** in the app's panel. The app adds Rectify, then opens Rectify in your browser to pick the project. To add it by hand instead, paste this into `~/.cursor/mcp.json` for Cursor or `~/.kiro/settings/mcp.json` for Kiro: ```json { "mcpServers": { "rectify": { "url": "https://api.rectify.so/v1/mcp" } } } ``` In VS Code, run **MCP: Open User Configuration** from the command palette and paste: ```json { "servers": { "rectify": { "type": "http", "url": "https://api.rectify.so/v1/mcp" } } } ``` Then select **Start** above the entry. In Cursor, open **Customize** in the sidebar and switch Rectify on if it's off. ## Antigravity 1. Open **Manage MCP Servers**, then **View raw config**. 2. Paste this, then select **Refresh** and **Authenticate** next to Rectify. ```json { "mcpServers": { "rectify": { "serverUrl": "https://api.rectify.so/v1/mcp" } } } ``` If sign-in doesn't start, use a key in the header, as in the next section. ## Claude Code, Windsurf and other clients These send your MCP key in an `Authorization` header. Paste the key exactly as you copied it. Claude Code, in a terminal: ```bash claude mcp add --transport http rectify https://api.rectify.so/v1/mcp --header "Authorization: Bearer YOUR_RECTIFY_KEY" ``` Run `claude mcp list`, or type `/mcp` in a session, to check it's connected. Windsurf: in the Cascade panel, open the **...** menu, then **Open MCP config file** under **MCPs**, and paste: ```json { "mcpServers": { "rectify": { "serverUrl": "https://api.rectify.so/v1/mcp", "headers": { "Authorization": "Bearer YOUR_RECTIFY_KEY" } } } } ``` Any other client that supports remote MCP servers over HTTP: use the server URL with the header `Authorization: Bearer YOUR_RECTIFY_KEY`. The panel for **Any MCP client** shows both, with your key filled in right after you create it. Keep the key out of shared files and out of git. Editors that open your MCP settings in a repository folder can commit them by accident. ## What the app can do The app acts as you. It sees what you can see in the project, and changes are made in your name. Some tools need an Owner or Admin, for example publishing help articles, writing changelog posts, sending email campaigns, approving or merging requests, assigning feedback, starting a fix, and changing roadmap boards, columns, tags or workflows. For a Member, those tools answer "Only workspace owners and admins can do this." ## Check it worked Ask your app "What feedback came in this week?". It answers from your project. On the MCP Server page, the app shows **Connected**, and apps that signed in show under **Connected apps**. ## Troubleshooting ### My app asks for an OAuth client ID Leave it empty. Rectify signs you in without one. If you paste a key there, Rectify refuses the connection. ### "Your Rectify MCP session has expired" The connection was idle or the server restarted. Reconnect Rectify from your app's settings, usually with a reconnect button next to it. ### "This connection was disconnected or has expired" Someone selected **Disconnect** under **Connected apps**, the app wasn't used for 90 days, or you signed out everywhere or reset your password. Connect again from the app. ### "MCP key not found or inactive" The key was revoked or deleted, or it was mistyped. Create a new key and update your app. ### "This key belongs to another teammate" Each person needs their own key. Create one on the MCP Server page. ### I can't select Claude Code, Windsurf or Any MCP client These need a key. Create one with **New key** first. ## Read next - [Manage MCP keys and connected apps](/rectify/help/a/87-manage-mcp-keys-and-connected-apps) - [Run the local MCP package](/rectify/help/a/88-run-the-local-mcp-package) - [Compare plans](/rectify/help/a/13-compare-plans) --- # Manage MCP keys and connected apps Collection: Developers URL: https://app.rectify.so/rectify/help/a/87-manage-mcp-keys-and-connected-apps Create, rename, revoke and delete MCP keys, see which AI apps use them, and disconnect apps that signed in with your Rectify account. > **Note:** **Before you start.** The MCP server needs the Build plan or higher. Anyone on your team can create keys for themselves. Owners and Admins also see their teammates' keys and connected apps, and can revoke or delete them. AI apps reach your project in one of two ways: with an MCP key you paste into the app, or by signing in with your Rectify account. You manage both on the MCP Server page: open **Project settings**, then **MCP server**. ## Create a key 1. On the MCP Server page, select **New key**. With no keys yet, select **Let's GO!**. 2. Name the key after where you'll use it, such as Work laptop or CI. The name is optional and can be up to 60 characters. 3. Select **Create key**. ![2 Name the key. 3 Create key.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106504449-01-new-key.png) 4. Copy the key from **Copy your key**, then select **Done**. ![Copy your key. The key is hidden here.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106505902-02-copy-key.png) The key is shown only this once. Rectify keeps only a fingerprint of it, so store it in a password manager. Until you leave the page, the connect steps on the page fill it in for you. The value you copy starts with `mcp_` and ends with a colon and your user ID. Paste it into your app exactly as copied. ## How keys work - A key belongs to the person who made it, and works with their role in the project. - Each key works in one project. - You can have up to 3 active keys in each project. Revoked keys don't count. - If you lose access to the project, your keys stop working. - If you lose a key, you can't see it again. Create a new one and revoke the old one. ## Your keys and team keys **Your keys** lists the keys you made. Owners and Admins also see **Team keys**, the keys their teammates made. Each key shows: - its name and whether it's **Active** or **Revoked** - the start and end of the key, with the middle hidden - who made it, for a teammate's key - when it was created, and **Used** with when an app last started a session with it - the apps that have used it ![Rename, Revoke and Delete, in a key's menu.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106507551-03-key-menu.png) ## Rename, revoke or delete a key Open the menu at the end of a key's row: - **Rename** changes the name shown on this page. Apps keep working. - **Revoke** turns the key off straight away. Every app using it loses access on its next request. The key stays in the list as **Revoked**, and you can't turn it back on. - **Delete** removes the key for good. Type `CONFIRM`, then select **Delete key**. Members can only rename, revoke or delete their own keys. ## Connected apps **Connected apps** lists the AI apps that signed in with a Rectify account, such as Claude or ChatGPT. It shows once an app has connected. Each row has the app's name, who connected it when it isn't you, when it connected, when it was last used and the address it sends you back to. Select **Disconnect** to cut an app off straight away. It has to sign in again to come back. Members see and disconnect their own apps. Owners and Admins see everyone's. A connected app also disconnects by itself: - after 90 days without use - when the person who connected it signs out of every device or resets their password - when that person loses access to the project - when that person connects more than 20 apps across all their projects, starting with the one used longest ago Keys don't change when you sign out everywhere or reset your password. Revoke them yourself if you need to. ## Check it worked After you revoke a key or disconnect an app, ask the app something about your project. It can no longer reach Rectify and asks you to connect again. ## Troubleshooting ### New key is greyed out Your organization is on the free Idea plan, and the MCP server needs Build or higher. Upgrade, or start the trial the page offers. ### "You can have up to 3 active MCP keys in a project" Revoke a key you no longer use, then create the new one. ### "You can only manage your own MCP keys" That key belongs to a teammate. Ask an Owner or Admin to revoke it. ### Used doesn't change while I use the app **Used** updates when an app starts a session with the key, not on every request. ## Read next - [Connect an AI app to Rectify over MCP](/rectify/help/a/86-connect-an-ai-app-to-rectify-over-mcp) - [Run the local MCP package](/rectify/help/a/88-run-the-local-mcp-package) - [Roles and project access: Owner, Admin and Member](/rectify/help/a/9-roles-and-project-access) --- # Run the local MCP package Collection: Developers URL: https://app.rectify.so/rectify/help/a/88-run-the-local-mcp-package Give your AI editor offline tools that map your codebase, with the @rectify-so/mcp package, and optionally read-only Rectify data. > **Note:** **Before you start.** You need Node.js 18 or newer, and an AI editor or CLI that runs local MCP servers, such as Cursor, Claude Code, VS Code or Claude Desktop. The repository tools work without a Rectify account. Adding Rectify data needs an MCP key, which needs the Build plan or higher. The local package, `@rectify-so/mcp`, runs on your computer next to your editor. It indexes your repository so your AI assistant can see how files and functions connect, what a change would affect and which tests cover it. Your code stays on your machine and is never sent to Rectify. It's separate from the hosted server. For everything Rectify can do, connect the hosted server as well, as [Connect an AI app to Rectify over MCP](/rectify/help/a/86-connect-an-ai-app-to-rectify-over-mcp) shows. ## Add it to your editor The MCP Server page shows these steps too. Open **Project settings**, **MCP server**, select your app, and look for **Add the local package**. ![Add the local package and Index once, in the Cursor panel on the MCP Server page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106510315-01-cursor-local.png) ### Cursor Paste this into `.cursor/mcp.json` inside your repository: ```json { "mcpServers": { "rectify-repo": { "command": "npx", "args": ["-y", "@rectify-so/mcp"] } } } ``` ### Claude Code Run this from the repository you want indexed: ```bash claude mcp add rectify-repo -- npx -y @rectify-so/mcp ``` ### VS Code Paste this into `.vscode/mcp.json` inside your repository: ```json { "servers": { "rectify-repo": { "type": "stdio", "command": "npx", "args": ["-y", "@rectify-so/mcp"] } } } ``` ### Claude Desktop, Windsurf and other editors These don't start inside your repository, so tell the package where it is with `--repo` and an absolute path: ```json { "mcpServers": { "rectify-repo": { "command": "npx", "args": ["-y", "@rectify-so/mcp", "--repo", "/absolute/path/to/your/repo"] } } } ``` For Claude Desktop, the file is `~/Library/Application Support/Claude/claude_desktop_config.json` on a Mac, or `%APPDATA%\Claude\claude_desktop_config.json` on Windows. Restart Claude Desktop after you save it. For Windsurf, it's `~/.codeium/windsurf/mcp_config.json`. ## Index your repository 1. Add `.rectify/` to your `.gitignore`. The index lives there. 2. Ask your assistant to run `update_memory`. 3. Run it again after big changes. It only reads files that changed since last time. The index is a file at `.rectify/repo-graph.json` in your repository. ## The tools | **Tool** | **What it does** | | --- | --- | | `update_memory` | Builds or refreshes the index. Takes an optional list of paths. | | `repository_overview` | Counts files and symbols, lists languages, the main modules and the most connected files. | | `architectural_summary` | Modules by folder, their key files and how they import each other. | | `trace_dependencies` | What a file or symbol depends on, what depends on it, or both. | | `find_related_files` | Files linked to a file or symbol through imports and calls. | | `analyze_impact` | What a change to a file or symbol would affect, including tests. | | `search_memory` | Finds files and symbols by name. | Only `update_memory` writes anything, and only to the index file. ## What gets indexed - **Languages:** TypeScript and JavaScript (`.ts`, `.tsx`, `.js`, `.jsx`, `.mjs`, `.cjs`, `.mts`, `.cts`) and Python (`.py`, `.pyi`). - **Skipped folders:** `.git`, `node_modules`, `dist`, `build`, `out`, `coverage`, `.next`, `.turbo`, `.cache`, `.venv`, `venv`, `__pycache__` and `.rectify`. - **Skipped files:** minified and bundled files, `.d.ts` files, files over 1.5 MB, and symbolic links. - Anything in the `.gitignore` at the root of your repository. - Anything in a `.rectifyignore` file at the root, written the same way as `.gitignore`. In JavaScript and TypeScript, imports that start with `./` or `../` are linked. Path aliases and package imports aren't. ## Options | **Option** | **What it does** | | --- | --- | | `--repo ` | The repository to index. The default is the folder the editor starts the package in. | | `--token ` | Your MCP key. Adds read-only Rectify data, below. | ## Add Rectify data With a key, the package also reads your project's feedback, code scans and monitoring. It can't change anything in Rectify. 1. Create a key on the MCP Server page, as [Manage MCP keys and connected apps](/rectify/help/a/87-manage-mcp-keys-and-connected-apps) shows. 2. Add `--token` and the key, exactly as you copied it, to the arguments. ```json { "mcpServers": { "rectify": { "command": "npx", "args": ["-y", "@rectify-so/mcp", "--token", "mcp_xxx:your_user_id"] } } } ``` The key must be in the form `mcp_xxx:your_user_id`, which is how **Copy your key** gives it to you. This config file now holds your key, so keep it out of git. With a key, your assistant gets one more tool, `rectify-feedback-session-url-analyze`, which analyses the recorded session of a feedback report. It can also read: - **Feedback:** the list, an overview, and a report's session analysis. - **Code Scan:** the latest scan, issues, issues by file, metrics and history. - **Monitoring:** an overview, monitors and their stats, incidents, and incident, slowest-monitor and lowest-uptime reports. ## Your code and privacy - The package never sends your code to Rectify. It only contacts Rectify when you pass a key, to read your Rectify data. - Tool results go to your AI assistant, like any file it reads. They include file paths, names of functions and classes, and the first line of each. - The index file holds the same details, which is why it belongs in `.gitignore`. ## Check it worked Ask your assistant to run `repository_overview`. After indexing, it lists your languages and main modules. To check the tools, list them from your editor: you'll see 7 tools, or 8 with a key. ## Troubleshooting ### The tools return "Repository not indexed yet" Ask the assistant to run `update_memory` first. Check that `--repo` points at the right folder, or that your editor starts the package inside the repository. ### "Invalid token format. Expected format: mcp_xxx:userId" Copy the key again from **Copy your key**, including the colon and your user ID after it. If you lost it, create a new key. ### The key doesn't work, but the repository tools do The package keeps running with only the repository tools when it can't use your key. Check the key is **Active** on the MCP Server page, that it's yours, and that your computer can reach `api.rectify.so`. ### My editor doesn't connect Restart the editor after changing its MCP settings. Check that `node --version` shows 18 or newer. ## Read next - [Connect an AI app to Rectify over MCP](/rectify/help/a/86-connect-an-ai-app-to-rectify-over-mcp) - [Manage MCP keys and connected apps](/rectify/help/a/87-manage-mcp-keys-and-connected-apps) --- # Install the extension and sign in Collection: Chrome extension URL: https://app.rectify.so/rectify/help/a/120-install-the-extension-and-sign-in Add Rectify for Chrome, agree to how it handles data and connect it to your Rectify account and project. > **Note:** **Before you start.** You need Chrome 116 or later and a Rectify account with at least one project you can open. The extension is free to install on every plan. Everyone signs in with their own Rectify account, so there's no key to share. Rectify for Chrome records bugs on any website, inserts your team's snippets in any text box and types with your voice. Everything it saves goes to the Rectify project you pick. ## Install and connect 1. Open [Rectify on the Chrome Web Store](https://chromewebstore.google.com/detail/baedommfdajjifmpollnnijkmemcffjh), select **Add to Chrome**, then **Add extension**. You can also get there from Rectify: open **Project settings**, then **Chrome extension**, and select **Add to Chrome**. ![1 Add to Chrome, at the top of the Chrome extension page in Rectify.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106680784-01-add-to-chrome.png) 2. A welcome tab opens. Read what each tool sends and when, then select **I agree**. ![2 I agree, under what each tool collects.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106682415-02-agree.png) 3. Select **Sign in with Rectify**. Rectify opens in a new tab. If you aren't signed in to Rectify in this browser yet, sign in first. ![3 Sign in with Rectify, on the welcome tab.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106684041-03-sign-in.png) 4. Under **Project**, pick the project your sessions and snippets should go to. If you belong to more than one organization, pick the **Organization** first. 5. Select **Connect Chrome**. ![4 Project. 5 Connect Chrome.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106685664-04-connect.png) The page says **Chrome is connected** and the tab closes on its own after a moment. To keep Rectify one click away, open the Extensions menu (the puzzle piece in Chrome's toolbar) and pin **Rectify**. ## Check it worked Select the Rectify icon in Chrome's toolbar. The popup shows your project at the top, **Record this tab** for the page you're on, and your **Snippets** and **Voice typing** shortcuts under **On every page**. ![The project name at the top of the Rectify popup.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106687306-05-popup-ready.png) ## Pick another project Select the project name at the top of the popup and choose another one. You can also select the gear for **Settings** and change **Project** there. The list shows only the projects you can open in Rectify, grouped by organization if you belong to more than one. ![The project list in the Rectify popup.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106689313-06-change-project.png) ## Stay signed in, or sign out The extension stays signed in as long as you use it at least once every 30 days. One account can connect up to 10 browsers. Connecting an eleventh signs out the one you used longest ago. To sign out, open the popup, select the gear for **Settings**, then **Sign out**. If a recording is running, signing out throws it away. You can also disconnect a browser from Rectify: open **Project settings**, then **Chrome extension**, open the menu on the browser and select **Disconnect**. Your browsers are listed under **Signed-in devices** on your profile too. [Set up the extension for your team](/rectify/help/a/125-set-up-the-extension-for-your-team) explains what Owners and Admins see. ### The extension says "Sign in to Rectify" again It says **You were signed out** when the browser was disconnected from Rectify, it wasn't used for 30 days, or you signed out everywhere from your profile. Select **Sign in with Rectify** to connect it again. ### It says "This link is incomplete" or "This sign-in has expired" The sign-in page was opened without the extension, or the sign-in took longer than 30 minutes. Open the Rectify popup and select **Sign in with Rectify** again. ### It says "Rectify for Chrome didn't answer" Check the extension is installed and turned on under Chrome's Extensions page, then select **Sign in with Rectify** in the extension again. ### It says "You need a project first" Your account has no project you can open. Create a project, or ask an Owner or Admin to give you access to one, then open the extension again. ### The shortcuts don't do anything Shortcuts stay off until you've selected **I agree** and signed in. Open the Rectify popup to finish both. Next, [record a session and report a bug](/rectify/help/a/121-record-a-session-and-report-a-bug). --- # Record a session and report a bug Collection: Chrome extension URL: https://app.rectify.so/rectify/help/a/121-record-a-session-and-report-a-bug Record what happens in a tab, with its console and network logs, and save it to your project as a bug report. > **Note:** **Before you start.** Sign in to the extension and pick a project first. Anyone who can open the project can record. A recording lasts up to 3 minutes, and each saved session counts toward your organization's extension sessions for the month. A session is a replay of what happened in one tab, with its clicks, console messages and network requests, plus your title and notes. Nothing leaves your browser until you select **Save session**. ## Record a session 1. Open the page where the problem happens. 2. Select the Rectify icon in Chrome's toolbar. 3. Select **Record this tab**. The popup closes and the recording starts. ![3 Record this tab, in the Rectify popup.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106691891-01-record.png) 4. Do what you did when it went wrong. A bar at the bottom of the page shows the time, the events recorded and any errors so far. 5. Select **Stop and save** in the bar. ![5 Stop and save, in the recording bar.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106693706-02-recording-bar.png) 6. Under **What went wrong?**, give the session a title. 7. Add what you did and what happened instead. This is optional. 8. Pick a priority: **Low**, **Medium**, **High** or **Critical**. It starts at **Medium**. 9. Select **Save session**, or press Ctrl+Enter (⌘ Enter on a Mac). ![6 Title. 7 What happened. 8 Priority. 9 Save session.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106695391-03-save.png) The card shows **Saved to** and your project name. Select **Open replay** to see the session in Rectify, or **Debug with Quanta** to open it with Quanta's tab ready. ![Debug with Quanta and Open replay, after the session is saved.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106697078-04-saved.png) You can also start and stop with Alt+Shift+R (Option+Shift+R on a Mac). To change that shortcut, open the popup, select the gear for **Settings**, then **Change recording shortcuts in Chrome**. To point at the exact thing that's wrong while you record, see [Point at a problem and pin a note](/rectify/help/a/122-point-at-a-problem-and-pin-a-note). ## What gets recorded - The tab's page, clicks and scrolls, as a replay. It keeps recording if you move to another page in the same tab. - Console messages and network requests, so you can see errors and failed calls. - The page address, how long you recorded and how many events there were. Two settings in the popup's **Settings**, under **Recording**, change what's kept: | **Setting** | **What it does** | **Starts** | | --- | --- | --- | | **Hide what people type** | Text typed into fields shows as dots in the replay. | On | | **Keep request and response bodies** | Keeps the content of network requests and responses. Passwords, tokens and headers like Authorization are always removed. | Off | These settings belong to your browser, so each teammate sets their own. > **Tip:** Building in Bolt, Lovable, v0, Replit or Base44? When your app's preview is open in the builder, Rectify records the preview, not the editor around it. ## Find your sessions in Rectify Open **Project settings**, then **Extension sessions**. Every session saved to the project is listed with its status and priority. Filter by **Unresolved**, **In progress** or **Resolved**, filter by priority, sort them, or search. ![The status filters and the sessions saved to Acme App.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106700502-05-sessions.png) Open a session to watch the replay and read its **Events**, **Console**, **Network**, **Quanta** and **Notes** tabs. Change the **Status** and **Priority** at the top as you work on it. The popup also lists the three latest sessions saved to the project for the site you're on, under **On this site**. Select **See all** to open **Extension sessions**. On the session's **Quanta** tab, select **Start debugging**. Quanta reads the console logs, network requests and clicks from the session, then lists what went wrong and when. It uses your organization's AI: your own AI provider key, or the AI credits included with paid plans. ## Sessions on each plan Every saved session counts toward one monthly allowance for your whole organization, across all its projects. It resets on the 1st of each month. | **Plan** | **Extension sessions a month** | | --- | --- | | Idea | 10 | | Build | 100 | | Launch | 1,000 | | Accelerate | 5,000 | | Enterprise | Unlimited | The popup shows how many sessions are left this month, under **Record this tab**. ### It says "No sessions left this month" Your organization has used this month's extension sessions. **Record this tab** stays off until the 1st, or until you move to a plan with more. See [Compare plans and what each one includes](/rectify/help/a/13-compare-plans). ### I can't record this page Chrome doesn't let extensions record its own pages, such as new tabs, settings and the Chrome Web Store. Open a website in the tab and try again. ### It says "Save or discard the last recording first" You stopped a recording without saving it. Open the Rectify popup, then save it with **Save session** or select **Discard** and confirm with **Discard recording**. ### The recording stopped on its own Recordings stop at 3 minutes. A very busy page can also hit the size limit sooner: the card then says the recording stopped early. Save what you have, or record a shorter session. ### I closed the save card, or the tab Selecting the X hides the card as **Recording ready to save** at the bottom of the page. Select it to bring the card back. If you closed the tab, the recording stops and you can still save it from the Rectify popup. Next, [point at a problem and pin a note](/rectify/help/a/122-point-at-a-problem-and-pin-a-note), or [set up the extension for your team](/rectify/help/a/125-set-up-the-extension-for-your-team). --- # Point at a problem and pin a note Collection: Chrome extension URL: https://app.rectify.so/rectify/help/a/122-point-at-a-problem-and-pin-a-note While you record, click the part of the page that's wrong and pin a note to it, so your team sees exactly where and when. > **Note:** **Before you start.** Pointing works while a recording is running. A session holds up to 49 pinned notes, and each note can be up to 2,000 characters. Notes are saved with the session when you select **Save session**. A pinned note is tied to one thing on the page and to the moment in the recording when you pinned it. Your team sees both next to the replay. ## Pin a note 1. Start recording the tab. [Record a session and report a bug](/rectify/help/a/121-record-a-session-and-report-a-bug) has the steps. 2. Select **Point at it** in the recording bar at the bottom of the page. The bar now says **Click anything to pin a note**. 3. Move over the page. An outline shows what you're pointing at. Click the part that's wrong. ![3 The outlined element, with the recording bar ready to pin.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106703073-01-pointing.png) 4. Write what's wrong in the note card. It shows the note's number and when in the recording you pinned it. 5. Select **Save note**, or press Ctrl+Enter (⌘ Enter on a Mac). ![4 The note. 5 Save note.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106704682-02-note.png) 6. Pin more notes the same way. When you're done, select **Done pointing** or press Esc. While you point, clicks on the page pin notes instead of pressing buttons, so you can point at a button without setting it off. Each pinned element shows its number while you're pointing. You can also start pointing from the Rectify popup with **Point at it**, or with Alt+Shift+P (Option+Shift+P on a Mac). To cancel a note before you save it, select **Cancel** or press Esc. ## Where your notes show up When you stop recording, the save card counts your notes, for example **2 notes**. After you save, open the session in **Project settings**, **Extension sessions** and select the **Notes** tab. Each pinned note shows the time in the recording and the element you pointed at. Select the time to jump to that moment in the replay. ![Pinned notes with their time and element on the Notes tab.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106706318-03-notes.png) If you described what happened when you saved the session, that note is listed first. Anyone who can open the project can add more notes from the box at the bottom of the tab. ### It says "Start recording first" Pointing needs a recording. Start one with **Record this tab** in the popup or Alt+Shift+R, then point. ### It says "A session holds up to 49 pinned notes" You've pinned the most one session can hold. Save this session and record another for the rest. Next, [save and reuse snippets](/rectify/help/a/124-save-and-reuse-snippets). --- # Speak instead of typing Collection: Chrome extension URL: https://app.rectify.so/rectify/help/a/123-speak-instead-of-typing Hold a shortcut in any text box on the web and talk. Rectify turns what you say into text where your cursor is. > **Note:** **Before you start.** Sign in to the extension and pick a project. You need a microphone. On the free Idea plan, voice typing is limited to 30 minutes a month, shared with dictation in Quanta; paid plans have no limit. Your audio goes to Rectify and its speech-to-text provider to become text, and Rectify doesn't keep it. ## Allow the microphone Chrome asks once before Rectify can use your microphone. On the welcome tab that opened when you installed the extension, select **Allow microphone** under **Voice typing uses your microphone**, then allow it when Chrome asks. If you skipped that step, Rectify shows **Rectify can't use your microphone yet** the first time you try. Select **Allow microphone** in that message to go back to the welcome tab. ## Type with your voice 1. Click in the text box where you want the text. 2. Press and hold Ctrl+Space. After a moment, a bar next to your cursor says **Listening**. Ctrl is the Control key on a Mac too. ![The Listening bar, with release to insert and the time.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106709050-01-listening.png) 3. Say what you want to write. 4. Let go of the keys. The bar says **Writing it down**, then your words appear where your cursor was. A quick tap doesn't start listening, so you need to hold the keys. Each take can last up to 2 minutes; at 2 minutes Rectify stops and writes what it heard. To throw a take away, press Esc while you're still holding the keys. Voice typing works in text fields, text areas and editors on any website. It doesn't work in password fields. ## Use a mic button instead 1. Open the Rectify popup and select the gear for **Settings**. 2. Turn on **Mic button in text boxes**. ![2 Mic button in text boxes, under On pages. The Voice typing shortcut is under Shortcuts.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106710733-03-settings.png) A mic button now shows inside a text box when you click into it. Select it to start listening, then select it again to stop and insert your words. ![The mic button in the corner of a text box.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106712554-02-mic-button.png) ## Change the shortcut or turn it off In **Settings**, under **Shortcuts**, select the keys next to **Voice typing**, then press the new combination. It needs at least one of Ctrl, Alt, Shift or ⌘, plus one other key. Press Esc to keep the old one. To turn voice typing off, use its switch under **On every page** in the popup. The shortcut and the mic button stop working until you turn it back on. ### It says "Chrome blocked the microphone for Rectify" The microphone was blocked for the extension. On the welcome tab, select **Open site settings**, set **Microphone** to allow, then come back and try again. ### It says "The microphone didn't start" Check that a microphone is connected, then try again. ### It says "Nothing was recorded" Keep holding the keys while you talk, and let go only when you've finished. ### It says "Voice typing limit reached for this month" You've used the 30 minutes included with the Idea plan this month. It resets on the 1st, or upgrade for unlimited voice typing. ### Ctrl+Space does something else on my computer Another app or your system may use the same keys. Pick a different shortcut in **Settings**, under **Shortcuts**. Next, [save and reuse snippets](/rectify/help/a/124-save-and-reuse-snippets). --- # Save and reuse snippets Collection: Chrome extension URL: https://app.rectify.so/rectify/help/a/124-save-and-reuse-snippets Keep the replies, templates and prompts you retype, and insert them in any text box on the web with one shortcut. > **Note:** **Before you start.** Snippets belong to a project, and there's no limit on any plan. Anyone who can open the project can create them. A snippet set to **Only me** is visible to you alone; a shared one is visible to everyone who can open the project. To use them in Chrome, sign in to the extension and pick the project. ## Insert a snippet 1. Click in a text box on any website. 2. Press Ctrl+\ to open the snippet picker. Ctrl is the Control key on a Mac too. ![The snippet picker, open in a reply box.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106715118-01-picker.png) 3. Type to search your snippets by title or text. Press Tab to move between **All**, **Favorites** and your most used categories. 4. Use the arrow keys and press Enter, or click a snippet. It goes in where your cursor was. Favorites come first, then the snippets changed most recently. Press Esc to close the picker without inserting anything. Placeholders such as {{first_name}} go in exactly as written, so fill them in before you send. ## Save a new snippet from the picker 1. In a text box, press Ctrl+\ and select **New snippet** at the bottom of the picker. 2. Name the snippet and type the text it inserts. The name needs at least 2 characters. 3. Pick a category. It starts at **Prompt**. 4. Select **Team** to share it with everyone in the project. Leave it off to keep it to yourself. 5. Select **Save snippet**, or press Ctrl+Enter (⌘ Enter on a Mac). ![3 Category. 4 Team. 5 Save snippet.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106716754-02-new-in-picker.png) ## Save text from any page 1. Open the Rectify popup, select the gear for **Settings**, and turn on **Save button on selected text**. 2. Select some text on a page, outside a text box, then select **Save as snippet**. ![2 Save as snippet, next to the selected text.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106718207-03-save-selection.png) 3. Name it, pick a category, choose **Team** if you want to share it, and select **Save snippet**. Rectify confirms with **Snippet saved. Insert it anywhere with your snippet shortcut.** ## Manage snippets in Rectify Open **Project settings**, then **Snippets**. Switch between **All**, **Shared** and **Only me**, sort by **Newest**, **Recently updated** or **Title A to Z**, or search. A lock marks the snippets only you can see. ![All, Shared and Only me, and New snippet, on the Snippets page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106719690-04-library.png) Open a snippet's menu to **View** it or **Add to favourites**. Favourites stay at the top of the list and of the picker. You can **Edit** and **Delete** only the snippets you created. Deleting one removes it from the library and from everyone's extension straight away, and it can't be undone. To create a snippet here: 1. Select **New snippet**. 2. Name it and type the text. Placeholders like {{first_name}} are fine. 3. Pick a category. 4. Choose **Only me** or **Everyone in project**. 5. Select **Save snippet**. ![3 Category. 4 Only me or Everyone in project. 5 Save snippet.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106721401-05-new-snippet.png) ## Change the shortcut or turn snippets off In the popup's **Settings**, under **Shortcuts**, select the keys next to **Open snippets** and press the new combination. It needs at least one of Ctrl, Alt, Shift or ⌘, plus one other key. To turn snippets off, use the **Snippets** switch under **On every page** in the popup. That also hides **Save as snippet**. ### Nothing happens when I press the shortcut Click into a text box first; the picker only opens where you can type. Check that **Snippets** is switched on in the popup and that you're signed in. ### A teammate can't see my snippet It's set to **Only me**. Open it in **Project settings**, **Snippets**, select **Edit** and choose **Everyone in project**. Your teammate also needs access to the same project, and their extension needs that project picked. ### The picker says "No snippets yet" Nobody has shared a snippet in this project and you haven't saved one. Select **New snippet** in the picker, or create one in Rectify. Next, [set up the extension for your team](/rectify/help/a/125-set-up-the-extension-for-your-team). --- # Set up the extension for your team Collection: Chrome extension URL: https://app.rectify.so/rectify/help/a/125-set-up-the-extension-for-your-team Get teammates recording and sharing snippets in the same project, see whose browsers are connected and disconnect one when you need to. > **Note:** **Before you start.** Each teammate needs their own Rectify account and access to the project. Owners and Admins can open every project; Members only the projects they're given. Only Owners and Admins see the team's browsers and can disconnect them. There's nothing to set up for the whole team at once. Everyone installs the extension and signs in with their own account, and their sessions and snippets are saved as them. ## Get your team started 1. Invite the people who'll use it, if they aren't in your organization yet. [Invite your team](/rectify/help/a/6-invite-your-team) has the steps. 2. Give Members access to the project they'll report bugs for, under **Organization settings**, **Members**. See [Roles and project access](/rectify/help/a/9-roles-and-project-access). 3. Send them the install link: [Rectify on the Chrome Web Store](https://chromewebstore.google.com/detail/baedommfdajjifmpollnnijkmemcffjh). They can also select **Add to Chrome** on the **Chrome extension** page under **Project settings**. 4. Ask each person to sign in and pick the project when they connect. [Install the extension and sign in](/rectify/help/a/120-install-the-extension-and-sign-in) walks them through it. ## Share snippets with everyone A snippet is shared when it's saved with **Team** in the extension, or with **Everyone in project** in Rectify. Everyone who can open the project, and has picked it in their extension, can then insert it. [Save and reuse snippets](/rectify/help/a/124-save-and-reuse-snippets) has the details. ## See who's connected Open **Project settings**, then **Chrome extension**. - **Your browsers** lists every browser you've connected, with its project, when it was connected and when it was last used. - **Team browsers** shows Owners and Admins the teammates whose extension is set to this project. ![The browsers connected to Acme App, under Team browsers.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106723770-01-team-browsers.png) ## Disconnect a browser 1. On the **Chrome extension** page, open the menu on the browser. 2. Select **Disconnect**. 3. Confirm with **Disconnect**. ![Disconnect, in the menu of a teammate's browser.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106725435-02-disconnect.png) That browser is signed out of Rectify straight away. Its owner can connect it again from the extension with **Sign in with Rectify**, as long as they still have access to the project. Each person can also disconnect their own browsers from their profile, under **Signed-in devices**. **Sign out everywhere else** there signs out every connected extension too. ## Good to know - **One allowance for the organization.** Every saved session counts toward your organization's extension sessions for the month, whoever recorded it and in whichever project. [Compare plans and what each one includes](/rectify/help/a/13-compare-plans) lists them. - **Recording settings belong to each browser.** **Hide what people type** and **Keep request and response bodies** are set by each person in their extension's **Settings**. - **Up to 10 browsers each.** Connecting an eleventh signs out the one used longest ago. - **No more extension keys.** Older versions of the extension used project API keys. This version doesn't need them, and the **Chrome extension** page links to **Old keys** if you want to review the ones left over. ### A teammate doesn't see our project in the extension They can only pick projects they can open in Rectify. Give them access under **Organization settings**, **Members**, then ask them to pick the project from the name at the top of the Rectify popup. ### I don't see Team browsers Only Owners and Admins see it, and only when a teammate's extension is set to this project. Members see their own browsers only. --- # Get the mobile app and sign in Collection: Mobile app URL: https://app.rectify.so/rectify/help/a/116-get-the-mobile-app-and-sign-in Download Rectify for iPhone, iPad or Android, sign in with the account you use on the web, and pick the project you want to work in. > **Note:** **Before you start.** You need a Rectify account and an organization. Both are created on the web, at [app.rectify.so](https://app.rectify.so); the app can't create accounts, organizations or projects. Members only see the projects they've been given. The Rectify app keeps your project with you. At the bottom of the app you'll find **Home**, **Inbox** and the round **Ask Quanta** button. At the top of **Home** and **Inbox** are your project's name, the bell for your notifications, and your photo, which opens **You**. ## Download the app | **Device** | **Get it from** | **Needs** | | --- | --- | --- | | iPhone and iPad | [App Store](https://apps.apple.com/us/app/rectify-app/id6766082124) | iOS or iPadOS 16.4 or later | | Android | [Google Play](https://play.google.com/store/apps/details?id=com.replicatetechnologiesltd.rectify) | Android 7.0 or later | On the App Store it's called **Rectify App**. On Google Play and on your home screen it's **Rectify**. ## Sign in 1. Open the app. 2. Tap **Sign in with email**. 3. Enter your **Email** and **Password**. 4. Tap **Sign in**. ![2 Sign in with email. 3 Email and Password. 4 Sign in.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794746832392-01-sign-in.png) To sign in with Apple, Google or GitHub instead, tap **Continue with Apple**, **Google** or **GitHub** on the first screen and approve Rectify. The Apple button is on iPhone and iPad only. Sign in the same way you do on the web, so you land in the same account. If your email address isn't verified yet, the app sends you a 6-digit code and opens **Verify your email**. Type the code from the email; the app checks it as soon as you enter the last digit. Then sign in again. New to Rectify? Tap **Create your workspace at rectify.so** at the bottom of the first screen, then **Open web app**. Create your account and organization on the web, then come back and sign in. ## Turn on notifications If your phone hasn't asked about Rectify notifications yet, the app shows **Know the moment it matters** after you sign in. 1. Tap **Turn on notifications**. 2. Allow notifications when your phone asks. **Not now** skips this. You can turn them on later under **You**, **Notifications**. ## Pick your project **Pick a project** lists your projects, grouped by organization, with your role next to each organization's name. Tap a project to open its **Home** screen. When you have more than one project, **Search projects** at the top finds one by name or website. ![Pick a project, with the projects in Acme Inc.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794746834925-02-pick-project.png) The app remembers your choice, so next time it opens straight on **Home**. New projects are created and set up on the web. ## Switch to another project 1. Tap your project's name at the top of **Home** or **Inbox**. 2. Under **Switch project**, tap the project you want. The one you're in has a check mark. ![1 Your project's name. 2 The project to switch to.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794751912616-03-switch-project.png) You can also tap your photo, then **Switch** next to the project's name. Projects from all your organizations are in the same list. ## Reset a forgotten password 1. On the first screen, tap **Sign in with email**. 2. Tap **Forgot?** in the password box. 3. Check your **Email** is filled in. 4. Tap **Send reset code**. 5. Type the 6-digit code from the email. The app checks it as soon as you type the last digit, and the code works for 5 minutes. 6. Enter a **New password** and type it again under **Confirm password**. Passwords need at least 8 characters. 7. Tap **Reset password**, then sign in with your new password. No email? Check your spam folder, then tap **Resend** under the code. You can ask for a new code once a minute. ## Your profile, appearance and signing out Tap your photo at the top of **Home** or **Inbox** to open **You**. - **Edit** at the top right opens **Edit profile**. Tap your photo to choose a new one, or tap **Remove photo**; photo changes save straight away. To change your **Name**, type it and tap **Save**. Your email address can't be changed in the app. - **Appearance** sets the app to **System**, **Light** or **Dark**. - **Help Center** opens these guides in your browser. - **Sign out** signs this phone out. It stops getting push notifications from Rectify until you sign in again. ![1 Edit. 2 Appearance. 3 Help Center. 4 Sign out.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794746838528-04-you.png) To sign the app out from another device, open your profile on the web and use **Signed-in devices**. [Sign in and keep your account secure](/rectify/help/a/12-sign-in-and-account-security) shows how. ## Troubleshooting ### It says "Invalid email or password" Check you're using the email address you signed up with. If you signed up with Apple, Google or GitHub, go back and tap that button instead. If you've forgotten your password, tap **Forgot?**. ### It says "No organizations yet" The account you signed in with isn't in any organization. You may have signed in a different way than on the web, for example with Apple or another email address. Tap **Sign out** at the top and sign in the way you do on the web. If it's the right account, ask an Owner or Admin of your organization to invite you. ### It says "No projects yet" under my organization There's no project in that organization that you can open. As a Member, you only see the projects you've been given, so ask an Owner or Admin for access. Owners and Admins create projects on the web. ### It says "Couldn't load these projects." Check your connection, then tap **Try again** under the organization's name. ### Resetting my password says "Invalid OTP", "OTP expired" or "Too many attempts" The code was wrong, more than 5 minutes old, or typed wrong 3 times. Tap **Resend** for a new code and type it in. ## Read next - [See what needs you on the Home screen](/rectify/help/a/128-see-what-needs-you-on-the-home-screen) - [Use Quanta and the canvas on your phone](/rectify/help/a/117-use-quanta-and-the-canvas-on-your-phone) - [Get alerts and push notifications on your phone](/rectify/help/a/119-alerts-and-push-notifications) --- # See what needs you on the Home screen Collection: Mobile app URL: https://app.rectify.so/rectify/help/a/128-see-what-needs-you-on-the-home-screen Read Quanta's briefing in the Rectify app, act on what needs you, check your week at a glance and open the latest Project Report. > **Note:** **Before you start.** Everyone who can open a project sees its **Home** screen in the app. The reports under **Last 24 hours** come from the Project Report, which only the organization's Owner can turn on. **Home** is the first screen of the app. Quanta checks the project you're in and shows what needs you, how your week is going and its latest reports. The line above the greeting says when, for example **Quanta · today at 9:41 AM**. Pull the screen down to check again. ## What needs you Under the greeting, Quanta tells you how many things need you, or says **Nothing needs you right now**. When there's a Project Report, **Read the 9:00 AM report ›** next to it opens the latest one. Each thing that needs you gets a card with two buttons. The first asks Quanta about it in a new chat. The second acts on it. ![1 Ask Quanta about it. 2 Act on it.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794751916992-01-needs-you.png) | **Card** | **Ask Quanta** | **Act** | | --- | --- | --- | | A monitor is down, for example **Sync service has been down for 2 hours** | **Ask why** | **Acknowledge** acknowledges the open incident on the monitor that's been down longest | | Posts and comments waiting for review on your portal | **Sort them** | **Review**, with the count, for example **Review 3**, opens the review queue in Rectify on the web | | Chats waiting for a reply that your team hasn't opened yet | **Summarize** | **Reply** opens **Inbox**, **Chats** | When nothing needs you, the **All clear** card lists what Quanta checked, for example **3 of 3 monitors up**, **Nothing waiting for review** and **No chats waiting for a reply**. ## This week Two tiles show your week at a glance: - **New feedback** counts the feedback that came in over the last 7 days, with the change from the 7 days before. Tap it to open **Inbox**, **Feedback**. - **Uptime today** shows your monitors' uptime on their latest day, and how many are up. Before there's any uptime to show, it says **Monitors up**. Projects without monitors see **Page views** for the last 7 days instead. ![1 This week. 2 Last 24 hours. 3 Ask Quanta.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794746844065-02-this-week.png) ## Last 24 hours This card shows up to 3 of the reports and alerts Quanta posted to the Project Report in the last 24 hours, newest first. Tap one to open it in the Project Report chat, or tap **Project Report ›** to open the whole chat. If reports are off, the card says **Reports are off**. The Owner can tap **Turn on** to open Quanta's settings and switch them on. [Heartbeat: scheduled check-ins and urgent alerts](/rectify/help/a/38-heartbeat-check-ins-and-alerts) explains what each report covers. ## Ask Quanta The chips at the bottom ask Quanta about your project in a new chat: **What changed this week?** and **Who might churn?**. When feedback came in this week, **Themes in this week's feedback** comes first. [Use Quanta and the canvas on your phone](/rectify/help/a/117-use-quanta-and-the-canvas-on-your-phone) shows what you can do in a chat. ## Troubleshooting ### It says "Couldn't load your briefing" Check your connection, then tap **Try again**. ### Review asks to open the web app The review queue isn't in the app yet. Tap **Open web app** to review posts and comments in Rectify on the web. You may need to sign in there. ### It says "No open incident for this monitor" That monitor has no open incident right now, so there's nothing to acknowledge. Pull the screen down to refresh it. ### It says "Ask an owner to turn on the Project Report." Only the organization's Owner can turn reports on. Ask them, or read [Heartbeat: scheduled check-ins and urgent alerts](/rectify/help/a/38-heartbeat-check-ins-and-alerts) to see what they'd get. ## Read next - [Triage feedback on your phone](/rectify/help/a/129-triage-feedback-on-your-phone) - [Answer support chats on your phone](/rectify/help/a/118-answer-support-chats-on-your-phone) - [Get alerts and push notifications on your phone](/rectify/help/a/119-alerts-and-push-notifications) --- # Triage feedback on your phone Collection: Mobile app URL: https://app.rectify.so/rectify/help/a/129-triage-feedback-on-your-phone Find feedback in the Rectify app, set its status, priority and owner, add notes, reply to the person who sent it, and move or delete it. > **Note:** **Before you start.** Everyone who can open a project can work through its feedback in the app. Moving and deleting feedback are for Owners and Admins. Replies to the person who sent feedback count toward your plan's Support Inbox replies, which are 10 a month on the free Idea plan. Feedback from your widget lands in **Inbox**, **Feedback**: the same reports your team sees on the web. Changes you make on your phone are saved to those reports, so your team sees them there too. ## Find feedback 1. Tap **Inbox**. 2. Tap **Feedback**. ![1 Inbox. 2 Feedback.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794746847100-01-find-feedback.png) The newest feedback is at the top, grouped by day. A red dot marks feedback from today and yesterday. Each row shows the title, how long ago it came in, the first line of the description, its type or status, the priority when it's **High** or **Critical**, and who sent it. A play icon means it has a session replay. The chips above the list narrow it down. The list starts on **Open** feedback. - **The status chip** picks **All statuses**, **Open**, **In progress**, **Under review** or **Resolved**. - **Bugs** shows bug reports only. - **High priority** shows **High** and **Critical** feedback. - **Assigned to me** shows feedback assigned to you. Tap a chip again to turn it off. Pull the list down to refresh it. Older feedback loads as you scroll. ## Assign or resolve from the list Swipe a row to the left for quick actions: - **Assign me** assigns the feedback to you. It doesn't show when it's already yours. - **Resolve** sets its status to **Resolved**. It doesn't show when it's already resolved. ![1 Assign me. 2 Resolve.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794746849344-02-swipe.png) ## Open a report Tap a row. The report shows its type, status and priority, the title, who sent it and the description, followed by any screenshots and recordings, **Assignee**, **Category**, the **Page** it was sent from, and the **Session** details. When the sender has a conversation linked to this feedback, **Chat** next to their name opens it. [Look into a bug report on your phone](/rectify/help/a/130-look-into-a-bug-report-on-your-phone) covers the recordings, logs and Quanta's triage. The arrows at the top move to the previous or next report in your list, and the middle shows where you are, for example **3 of 42**. **Inbox** takes you back to the list. ## Set the status, priority, type or category 1. Tap **Status** at the bottom of the report. 2. Tap the new value under **Status**, **Priority**, **Type** or **Category**. It saves straight away. 3. Tap **Done**. ![1 Status. 2 The new value. 3 Done.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794751920218-03-status.png) | **Section** | **Choices** | | --- | --- | | **Status** | **Open**, **In progress**, **Under review**, **Resolved** | | **Priority** | **Low**, **Medium**, **High**, **Critical**, **Neutral** | | **Type** | **Bug**, **Idea**, **General**, **Testimonial** | | **Category** | **Improvement**, **Suggestion**, **Task**. You can pick more than one. | To give it an owner, tap **Assignee** in the report and pick a teammate. The list only shows teammates who can open this project. ## Add a note for your team 1. Tap **Note** at the bottom of the report. 2. Type your note. Notes can be up to 1,000 characters. 3. Tap **Add note**. Reporters never see notes. Notes show under **Notes** at the end of the report. Tap **•••** on a note to **Edit** it, **Mark resolved** or **Delete** it. ## Reply to the person who sent it **Reply** works when the feedback has the sender's email address. 1. Tap **Reply** at the bottom of the report. 2. Type your message. 3. Tap **Reply** or **Invite** at the top right, whichever the sheet shows. ![1 Reply. 2 Your message. 3 Invite.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794751924181-04-reply.png) - **Reply** shows when they already have a conversation with your team. Your message goes into that conversation, linked to this feedback. To start a fresh conversation, tap **Start a new chat instead**. - **Invite** emails them an invite that opens the chat widget on the page they sent the feedback from. The **Reply to user** and **Internal note** switch at the top of the sheet changes between a reply and a note. ## Edit, move or delete it Tap **•••** at the top right of the report: - **Edit** changes the **Title** (3 to 200 characters), **Description**, **Type**, **Status**, **Priority**, **Categories** and **Assignee**. Tap **Save** when you're done. - **Move** moves the feedback to another project in your organization. - **Delete** deletes it after you confirm. It can't be undone. ## Troubleshooting ### It says "No open feedback" The list starts on **Open** feedback, and there's none right now. Tap **Show all statuses** to see the rest. ### It says "No feedback matches these filters" Tap **Reset filters**, or turn a chip off. ### Reply is greyed out The feedback has no email address for the person who sent it, so there's no one to reply to. Add a note for your team instead. ### It says "Replying to reporters needs a higher plan." Your team has used this month's 10 replies on the free Idea plan. Upgrade, or wait until next month. [Compare plans and what each one includes](/rectify/help/a/13-compare-plans) lists the limits. ### It says "Cannot invite: this report has no page URL to open the chat on." The invite opens the chat widget on the page the feedback came from, and this report doesn't have one. Contact the person another way. ### Move and Delete are greyed out They're for Owners and Admins. Ask one of them to move or delete the feedback. ## Read next - [Look into a bug report on your phone](/rectify/help/a/130-look-into-a-bug-report-on-your-phone) - [Answer support chats on your phone](/rectify/help/a/118-answer-support-chats-on-your-phone) - [Triage feedback: status, priority, owner and notes](/rectify/help/a/26-triage-feedback) --- # Look into a bug report on your phone Collection: Mobile app URL: https://app.rectify.so/rectify/help/a/130-look-into-a-bug-report-on-your-phone Watch the session replay, read the technical logs, run Quanta's triage and ask Quanta about a bug report, all from the Rectify app. > **Note:** **Before you start.** Replays and logs come with bug reports sent from the widget's **Report a Bug** form. The console, network and action logs need the Build plan or higher. Quanta's triage and chat use your organization's AI: your own AI provider key, or the AI credits included with paid plans. Only Owners and Admins can ask Quanta to write a fix. Open a report from **Inbox**, **Feedback**. Under the description, a row of tiles shows everything that came with it: **Session replay**, **Video**, the screenshots, **Technical logs** and **Attachment**. Only the ones the report has are there. ![The tiles under a bug report: Session replay, a screenshot and Technical logs.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794746858074-01-tiles.png) ## Look at what was sent - **Screenshots:** tap one to see it full screen, and swipe to the next. When there are more than 4, the last tile shows how many more. - **Video:** plays in the app. Loom videos open in your browser. - **Attachment:** opens the file in your browser. ## Watch the session replay 1. Tap **Session replay**. 2. Play the recording of what the person did before they sent the report. 3. Under **Event Timeline**, tap an event to jump to that moment. **Search events...** and **Major only** narrow the list. ![2 Play. 3 An event in the Event Timeline.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794746861871-02-replay.png) **Analysis & Chat**, next to **Event Timeline**, has Quanta explain the session. Tap **Let's GO!** for a summary, then ask your own questions about what the person did. ## Read the technical logs 1. Tap **Technical logs**. 2. Pick **Console**, **Network** or **Actions**. ![2 Console, Network and Actions.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794746864161-03-logs.png) **Console** has the errors, warnings and logs from the person's browser. **Network** has the requests their browser made, with status codes. **Actions** has their clicks, key presses and page changes. Tap **Done** to close the logs. ## Triage a bug with Quanta Bug reports have a Quanta card below the tiles. Until Quanta has looked at the bug, it says **Triage with Quanta**. 1. Tap **Triage with Quanta**. 2. Optionally, tap **Model** and pick one. **Auto (recommended)** lets Rectify choose. 3. Tap **Start triage**. ![1 Triage with Quanta. 2 Model. 3 Start triage.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794746866441-04-triage.png) You can tap **Done** and keep working while Quanta looks into it. When it's finished, the card shows a short summary. Tap **See the report** for the **Likely root cause**, **Suspect files**, **Reproduction steps** and **Suggested fixes**. **Re-triage** runs it again, for example after you connect GitHub. With GitHub connected to a repository, Owners and Admins also see **Fix with Quanta**. Tap it, then **Start fix**, and Quanta opens a draft pull request for your team to review. Nothing is merged without your review. [Triage and fix bugs with Quanta](/rectify/help/a/28-triage-and-fix-bugs-with-quanta) explains what a fix needs. ## Ask Quanta about the report 1. Tap the round **Ask Quanta** button at the bottom right of the report. 2. Choose what Quanta can read: **Session logs**, **Screenshots** and **Attachment**. Tap one to leave it out. 3. Type your question in the **Ask Quanta about this feedback...** box. 4. Tap the send arrow. ![1 Ask Quanta. 2 What Quanta can read. 3 Your question. 4 Send.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794751932858-05-ask-quanta.png) Each report has one Quanta chat, and your team sees the same chat, so it's there when anyone comes back to the report. ## Troubleshooting ### It says "Technical logs need a higher plan." Console, network and action logs come with the Build plan and higher. [Compare plans and what each one includes](/rectify/help/a/13-compare-plans) lists what each plan has. ### It says "Reading images needs your own Gemini key." Quanta reads screenshots and images with Gemini, so it needs your organization's own Gemini key. An Owner or Admin can add one on the web under **Organization settings**, **AI providers**. ### It says "Only admins and owners can start a Quanta fix." Ask an Owner or Admin to start the fix, or to change your role. ### It says "Session playback failed" The recording couldn't be played, often because there's too little in it. The rest of the report, including the technical logs, is still there. ## Read next - [Triage feedback on your phone](/rectify/help/a/129-triage-feedback-on-your-phone) - [Watch a session replay and its debug logs](/rectify/help/a/27-watch-a-session-replay) - [Triage and fix bugs with Quanta](/rectify/help/a/28-triage-and-fix-bugs-with-quanta) --- # Answer support chats on your phone Collection: Mobile app URL: https://app.rectify.so/rectify/help/a/118-answer-support-chats-on-your-phone Find a conversation in the Rectify app, join or take it over, reply with text, a photo or a PDF, let Quanta help, and keep notes. > **Note:** **Before you start.** Everyone who can open a project can join, take over and answer its chats in the app. Assigning, priority, **Done**, **Archive**, notes and deleting are for Owners and Admins. On the free Idea plan, your team can send 10 replies a month, counted together with replies sent from the web. Quanta's answers don't count. Your support conversations are under **Inbox**, **Chats**, for the project you're in. They're the same conversations your team sees on the web, and replies show up in both places straight away. ## Find a conversation 1. Tap **Inbox**. 2. Tap **Chats**. ![1 Inbox. 2 Chats.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794751941120-01-find-chats.png) The list shows the chats handed to your team and the chats Quanta is still answering. Quanta's chats have a chip with its name and picture, or the name and picture you gave it in your widget. Chats with new messages come first, with a red dot, and the number on **Inbox** and **Chats** counts them. New chats and messages appear as they arrive. The chips above the list narrow it down: - **The magnifier** searches customer names and message text. - **The status chip** picks **Open**, **Done** or **Archived**. Archived chats only show when you pick **Archived**. - **Unassigned** shows chats nobody has, **Assigned** shows chats assigned to you, and **Quanta** shows only the chats Quanta is still answering. - **The priority chip** picks **Urgent**, **High**, **Medium** or **Low**. - **Clear** turns the filters off. Pull the list down to refresh it. ## Reply to a customer 1. Tap a conversation. The customer's name is at the top, with **Online** or **Offline** under it. 2. If it says **No one has joined this chat yet**, tap **Join**. The chat is assigned to you. 3. Type your reply in the box at the bottom. 4. Tap the send arrow. ![2 Join. 3 The message box. 4 Send.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794751943531-02-reply.png) Tap **+** next to the box for more: - **Photo** or **PDF document** adds a file to your message. You can send one file with each message, up to 10 MB. - **Mention a teammate** brings a teammate in, and they get an alert. You can also type **@**. - **Link feedback** links a feedback item. You can also type **#**. You can link up to 5 in one reply. - **Ask Quanta** works like typing **/**, below. ![The menu under +: Ask Quanta, Mention a teammate, Link feedback, Photo and PDF document.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794751945998-03-more.png) > **Warning:** A mention or a linked item is part of your reply, so the customer sees it too. Anything only your team should read belongs in the conversation's notes. Press and hold a message for **Reply** and **Copy text**. On your own messages, you'll also find **Edit** and **Delete**. ## Take over from Quanta While Quanta is still answering a chat, you can read it but not type in it. In place of the message box, a bar says **Quanta is handling this chat**, with the name you gave Quanta in your widget if you changed it. 1. In **Chats**, tap a chat with Quanta's chip. To see only those chats, tap **Quanta** above the list. 2. Tap **Take Over** in the bar at the bottom. ![1 A chat Quanta is answering. 2 Take Over.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794751948268-04-take-over.png) The chat moves to your team and is assigned to you, and the customer is told they're now connected with your team. Type your reply as usual. [Choose who answers first: Quanta or your team](/rectify/help/a/30-choose-who-answers-first) explains when chats move from Quanta to your team. ## Let Quanta help you reply 1. In an empty message box, type **/**. 2. Pick what you need: - **Draft a reply:** Quanta answers the customer's latest message for you to check. - **Summarize conversation:** the key points so far. - **Find related feedback:** feedback, requests and earlier chats from this person. - **Analyze attachments:** screenshots, session replays and documents from this person's feedback. 3. When the answer is ready, tap **Insert into reply** to use it, or **Copy**. ![2 Quanta's commands, starting with Draft a reply.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794751950791-05-ask-quanta.png) To ask your own question, type it after the **/**, then tap the **Ask Quanta:** line that shows your question. Nothing reaches the customer until you send it yourself. To polish what you wrote, select at least 10 characters of it and tap **Enhance message**, **Fix grammar** or **Enhance and fix grammar**. Quanta's face at the top of the conversation opens a longer chat with Quanta about it. ## Keep notes and change the details Tap the customer's name at the top to open the **Conversation** panel. It shows who you're talking to, with **View full profile** when they're one of your contacts. Owners and Admins can: - **Assign** the chat to a teammate. The list only shows teammates who can open this project. - Set the priority to **Urgent**, **High**, **Medium**, **Low** or **None**. - Tap **Done** to close the chat, or **Reopen** to open it again. - Tap **Archive** to take it out of the list without telling the customer, or **Unarchive** to bring it back. - Write a private note under **Notes** and tap **Save Note**. Customers never see notes. ![The Conversation panel: Assign, priority, Done and Archive, then Notes.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794746884520-06-conversation-panel.png) Below that are the **Conversation log**, the customer's **Guest specifications** and the **Past feed** of earlier conversations with them. **Delete conversation** deletes the chat and everything in it after you confirm. It can't be undone. ## Get alerts for new chats To hear about chats when the app is closed, tap your photo, then **Notifications**, and switch these on under **Support**: - **Support Session Started:** a visitor starts a support conversation, with Quanta or your team. - **Human Support Requested:** a customer asked to talk to your team. - **Support Inbox Message:** a customer wrote in a conversation that's yours, or in one nobody is assigned to. - **Support Chat Assigned:** a conversation was assigned to you. - **Mentioned in Conversation:** a teammate mentioned you. Tapping one of these alerts opens the conversation. [Get alerts and push notifications on your phone](/rectify/help/a/119-alerts-and-push-notifications) has the details. ## Troubleshooting ### I can't type a reply Quanta is still answering this chat. Tap **Take Over** in the bar at the bottom to answer it yourself. ### It says "In order to continue using this feature, please upgrade your plan." Your team has used this month's 10 replies on the free Idea plan, so the send button stays grey. An Owner or Admin can upgrade on the web, or you can wait until next month. [Compare plans and what each one includes](/rectify/help/a/13-compare-plans) lists the limits. ### It says "Chat is already assigned to an agent" A teammate joined first. Pull the list down to refresh it and see who has the chat. ### It says "File size exceeds the limit of 10MB." Pick a smaller file, or send a link to it instead. ### Assign, Done and Archive are greyed out, and I can't type a note They're for Owners and Admins. They're also off while Quanta is still answering the chat; tap **Take Over** first. ## Read next - [Answer chats in the support inbox](/rectify/help/a/32-answer-chats-in-the-support-inbox) - [Triage feedback on your phone](/rectify/help/a/129-triage-feedback-on-your-phone) - [Get alerts and push notifications on your phone](/rectify/help/a/119-alerts-and-push-notifications) --- # Use Quanta and the canvas on your phone Collection: Mobile app URL: https://app.rectify.so/rectify/help/a/117-use-quanta-and-the-canvas-on-your-phone Ask Quanta from the Rectify app, open its canvas, approve the changes it prepares, talk instead of typing, and find your chats again. > **Note:** **Before you start.** Everyone who can open a project can chat with Quanta in the app. Quanta runs on your own AI provider key, or on the Rectify credits that come with paid plans. A few changes are for Owners and Admins only, and only the organization's Owner can change Quanta's settings. Quanta works in the project you're in. [Get the mobile app and sign in](/rectify/help/a/116-get-the-mobile-app-and-sign-in) shows how to switch projects. ## Ask Quanta something 1. Tap the round **Ask Quanta** button at the bottom of **Home** or **Inbox**. 2. Type your question where it says **Ask anything about** and your project's name. 3. Tap the send arrow. ![2 Ask anything about Acme App. 3 Send.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794751953883-01-ask.png) The chat opens and Quanta answers there. Quanta names the chat from your first message. To keep going, type a follow-up in the box at the bottom. Not sure where to start? - **Suggested now** lists questions about what's happening in your project. Tap one to ask it straight away. - **Feedback**, **Code Scan**, **Monitor**, **Report**, **Roadmap** and **General** each open a list of questions. The one you pick goes into the box, so you can change it before you send. The chip next to **+** shows the model. **Best** picks one for you. Tap it to choose a model from the AI providers your organization can use. In an open chat, tap **+**, then the **Model** line. To add files, tap **+**, then **Photo** or **PDF document**. You can add up to 3 files to a message, up to 10 MB each. Type a message to send them with. ## Open the canvas When you ask Quanta to show something, like your feedback, your roadmap or your monitors, it opens the full view in a canvas that slides up from the bottom of the screen. - To close the canvas, swipe it down or tap **Done**. - Under Quanta's reply, a card with the canvas's name brings it back. It says **Open canvas** or **Close canvas**. - Small cards inside a reply can have **Open**. Tap it and Quanta opens the full view in the canvas. ![1 Done closes the canvas. 2 The card under Quanta's reply opens it again.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794751956266-02-canvas.png) The app has its own canvas views for most of Rectify, from feedback and chats to campaigns, surveys and workflows. Anything else shows as a simple list of details. ## Approve a change Quanta never changes anything until you confirm it. 1. Ask Quanta for a change, for example "Log a bug: the checkout button does nothing on Safari. High priority." 2. Check the card that appears in the chat. It sums up the change and lists what will be saved. A warning in red tells you when a change can't be undone. 3. Tap **Confirm**. ![2 The card that sums up the change. 3 Confirm.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794751958793-03-approve.png) The card then says **Done** or **Failed**, and a message tells you what happened. Not ready? Tap **Cancel**. Nothing is saved, and the card says **Canceled**. A few things to know: - A change waits 30 minutes. After that, ask Quanta to prepare it again. - Only the person who asked can confirm a change. ## Answer Quanta's questions When Quanta needs details, it shows a short form above the message box instead of guessing. 1. Tap an answer, or type your own. 2. Tap **Continue** to go to the next question. 3. On the last question, tap **Send**. To skip the questions, tap the **X** on the form. The reply is then marked **Canceled**. ## Copy or retry a reply Under Quanta's replies, the copy icon copies the text, and the circular arrow asks again and replaces the reply. Quanta can make mistakes, so check anything important before you act on it. ## Talk to Quanta 1. Tap the waveform next to the message box. In **Ask Quanta**, this starts a new chat. 2. Allow Rectify to use the microphone, if your phone asks. 3. Talk once it says **Listening**. 4. Tap the red **X** when you're done. While you talk, the microphone button mutes you. The speech bubble button shows the chat, with a bar at the top that keeps the voice chat going; tap **End** on the bar to finish. Everything you both say is saved in the chat as text. [Talk to Quanta with your voice](/rectify/help/a/37-talk-to-quanta-with-your-voice) covers voices and languages. ## Find your chats again 1. Tap **Ask Quanta**. 2. Tap the clock at the top, or **All chats** next to **Recent**. 3. Tap a chat to open it. ![2 The clock. 3 A chat in Chats.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794751961249-04-chats.png) **Chats** lists your chats in this project under **Starred**, **Today**, **Yesterday**, **This week** and **Earlier**, and older ones load as you scroll. **Search your chats** finds one by name. When you've also talked to Quanta about feedback, replays, support chats, analytics or extension sessions, chips at the top filter by where the chat started. The Project Report chat sits at the top. Swipe a chat to the left to **Star** or **Delete** it, or press and hold it for **Star**, **Rename**, **Share** and **Delete**. In an open chat, tap **•••** at the top right. For chats started somewhere else, like on a feedback report, **Remove from history** takes them off this list instead. Deleting a chat can't be undone. Chats you don't touch for a while are deleted. Scroll to the top of a chat to see when; every new message starts the clock again. [Ask Quanta and approve its changes](/rectify/help/a/35-ask-quanta-and-approve-changes) lists how long each plan keeps a chat. ## Quanta's settings Tap the gear at the top of **Chats**, or tap your photo, then **Quanta**. **Quanta settings** has three parts: - **Project report:** Quanta's scheduled checks of your project. The switch at the top, for example **Check Acme App on a schedule**, turns them on. Pick **How often**, how Quanta tells you under **Tell me by** (**Push**, **Email**, **Phone call** or **SMS**), and the **Notification frequency**. **Project Report chat** opens the reports. - **Voice:** the **Voice**, **Language** and **Personality** Quanta uses when it talks. - **Phone and SMS:** phone calls from Quanta about critical problems. This needs Twilio, which you connect on the web. ![Quanta settings: Project report, Voice, and Phone and SMS.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794746898296-05-settings.png) Changes save as you make them. Everyone can look, but only the organization's Owner can change them. [Heartbeat: scheduled check-ins and urgent alerts](/rectify/help/a/38-heartbeat-check-ins-and-alerts) explains each setting. ## Troubleshooting ### It says "Action not found or expired. Ask Quanta to prepare it again." The change waited too long, usually more than 30 minutes. Ask Quanta for it again. ### It says "This action does not belong to you." Someone else asked for this change, so only they can confirm it. Ask Quanta for it in your own chat. ### It says "Failed to access microphone. Please check permissions." Rectify isn't allowed to use the microphone. On iPhone, open **Settings**, then **Rectify**, and turn on **Microphone**. On Android, open your phone's settings, find Rectify under your apps and allow the microphone. Then try again. ### It says "Only the organization owner can change Quanta settings. You're viewing in read-only mode." You can see Quanta's settings, but only the Owner can change them. ### It says "Only the owner of this chat can ask Quanta here." This Project Report chat belongs to a teammate. You can read it, but only they can write in it. ### It says "You can only upload a maximum of 3 files." Each message takes up to 3 files. Send the rest with your next message. ### It says "Invalid file type. Only JPEG, PNG, WebP images and PDF are allowed." Quanta takes photos in those formats and PDF documents. Save the file in one of them, or send a screenshot of it instead. ## Read next - [See what needs you on the Home screen](/rectify/help/a/128-see-what-needs-you-on-the-home-screen) - [Answer support chats on your phone](/rectify/help/a/118-answer-support-chats-on-your-phone) - [Work with canvas panels and Expand](/rectify/help/a/36-canvas-panels-and-expand) --- # Get alerts and push notifications on your phone Collection: Mobile app URL: https://app.rectify.so/rectify/help/a/119-alerts-and-push-notifications Turn on Rectify's push notifications, choose which alerts you get, and read and act on your notifications in the Rectify app. > **Note:** **Before you start.** Push notifications reach every phone where you're signed in to the Rectify app and have allowed notifications. Your alert choices are your own, set separately for each organization, and they apply on every device where you get Rectify notifications. Members only get alerts for the projects they can open. ## Turn on push notifications If your phone hasn't asked about Rectify notifications yet, the app offers **Turn on notifications** after you sign in. Tap it, then allow notifications when your phone asks. To turn them on later, or to check them: 1. Tap your photo at the top of **Home** or **Inbox**. 2. Tap **Notifications**. 3. Turn on **Push notifications**. ![2 Notifications. 3 Push notifications.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794751963959-02-turn-on.png) When it's on, it says **On for** and your organization's name. If it says **Turned off in your phone's Settings**, your phone is blocking Rectify: tap **Open Settings** and allow notifications there. On Android 12 and earlier, notifications are on unless you turn them off in your phone's settings. > **Warning:** **Push notifications** covers the whole organization, not only this phone. Turning it off stops push notifications from this organization on all your devices, and Rectify on the web shows it as off too. Rectify links your phone to your account when you sign in. **Sign out** on the **You** screen stops push notifications on that phone. ## Choose which alerts you get 1. Tap your photo, then **Notifications**. 2. Under **Alerts**, keep **Push** selected, or tap **Email** for the alerts you get by email. 3. Switch each alert on or off. Changes save straight away. ![2 Push or Email. 3 An alert's switch.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794746903887-03-choose-alerts.png) Push alerts are grouped into **Billing & Subscription**, **Team**, **Feedback**, **Feature Requests & Roadmap**, **Support**, **Automation & AI**, **Code Analysis**, **Monitoring** and **Changelog**. Email alerts go to the address you sign in with. Most alerts start switched on. The same choices show in Rectify on the web; [Your profile and notification settings](/rectify/help/a/11-profile-and-notification-settings) covers that page. Quanta can also send a push when one of its scheduled checks finds something that needs you. The organization's Owner turns this on with **Push** under **Tell me by** in Quanta's settings. [Heartbeat: scheduled check-ins and urgent alerts](/rectify/help/a/38-heartbeat-check-ins-and-alerts) explains how it works. ## What happens when you tap a notification - **Support alerts** open the conversation, ready for your reply. - **Feedback alerts** open the feedback. - **Quanta's alerts**, like a Project Report, open the chat. - **Everything else** opens **Notifications**, with that alert open. If the alert belongs to another organization or project, the app switches to it first and tells you, for example "Switched to Acme Inc". ## Read your notifications in the app Tap the bell at the top of **Home** or **Inbox**. A red dot on the bell means you have unread notifications. - **Unread**, **All** and **Read** at the top filter the list. **Unread** shows how many there are. - **Needs action** at the top lists what needs you in this project, with a button to act on each, like on **Home**. - Tap a notification to mark it read. Support, feedback and Quanta notifications open where they point; the others open up to show the full message, who it's from and when. - Swipe a notification to the left and tap **Read** to mark it read without opening it. - **Mark all read** at the top marks everything read. ![1 Unread, All and Read. 2 Needs action. 3 Mark all read.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1794746906218-04-notifications.png) Pull the list down to refresh it. Older notifications load as you scroll. The list shows the organization you're in; switch to a project in another organization to see its notifications. ## Troubleshooting ### I don't get any push notifications Check these in order: 1. Notifications for Rectify are allowed in your phone's settings. 2. You're signed in to the app with the same account you use on the web. 3. **Push notifications** is on under **You**, **Notifications**. Check it while you're in a project of the organization you expect alerts from, since each organization has its own setting. 4. The alerts you expect are switched on under **Alerts**, **Push**. ### The alert switches are greyed out **Push notifications** is off, or your phone is blocking Rectify. Turn it on, or tap **Open Settings** to allow notifications. ### Alerts from one project never arrive As a Member, you only get alerts for projects you can open. Ask an Owner or Admin to give you access to that project. ### Tapping a notification says "You don't have access to this organization" You're no longer a member of the organization that sent it. Ask one of its Owners or Admins to invite you again. If it says "You don't have access to this project", ask them for access to that project. ## Read next - [Answer support chats on your phone](/rectify/help/a/118-answer-support-chats-on-your-phone) - [See what needs you on the Home screen](/rectify/help/a/128-see-what-needs-you-on-the-home-screen) - [Your profile and notification settings](/rectify/help/a/11-profile-and-notification-settings) --- # Roles and project access: Owner, Admin and Member Collection: Account, team and billing URL: https://app.rectify.so/rectify/help/a/9-roles-and-project-access What each role can do, and how to change someone's role or the projects they can open. Everyone in an organization has one of three roles. You can see each person's role and the projects they can open under **Organization settings**, **Members**. ![Each person's role and project access on the Members page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106039548-01-members-roles.png) | **Role** | **What they can do** | | --- | --- | | **Owner** | Everything. The Owner is the person who created the organization. There is one Owner, and the Owner can't be changed or removed. | | **Admin** | Everything in every project, plus organization settings, members, invitations and billing. Only the Owner can delete a project. | | **Member** | Works in the projects they're given: feedback, roadmap, changelog, help center, widget, monitoring and more. They can view organization settings but can't change them, and can't invite people. | A few settings belong to the Owner alone, such as Quanta's project settings and redeeming a license. ## Change someone's role or projects > **Note:** **Before you start.** Only Owners and Admins can change roles. 1. Open **Organization settings**, then **Members**. 2. Open the menu on the person's row and select **Edit Member**. 3. Change their **Role**, or the projects under **Project Access**. 4. Select **Save Changes**. ![3 Role and Project Access. 4 Save Changes.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106040973-02-edit-member.png) Making someone an Admin gives them every project. A Member needs at least one project. ## Remove someone 1. Open the menu on their row and select **Remove**. 2. Confirm with **Remove**. Removing someone can't be undone. To bring them back, invite them again. ### Can I change who the Owner is? No. The Owner role stays with the person who created the organization, and it can't be given to someone else. --- # Manage your organization settings Collection: Account, team and billing URL: https://app.rectify.so/rectify/help/a/10-manage-organization-settings Change your organization's name and logo, and find its plan, owner and ID. > **Note:** **Before you start.** Owners and Admins can change these settings. Members can view them. ## Change the name or logo 1. Open **Organization settings**, then **General**. 2. Next to **Logo**, select **Upload** and pick a square image up to 5 MB. 3. To rename the organization, select the pencil next to **Name** and type the new name. An amber dot means the change isn't saved yet. 4. Select **Save changes** at the top of the page. ![2 Upload a logo. 3 Edit the name. 4 Save changes.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106043611-01-general.png) The name shows in the top bar, in emails and in invitations. ## What else is on this page | **Item** | **What it's for** | | --- | --- | | **Slug** | Set when the organization was created. It can't be changed. | | **Organization ID** | Copy it with the button next to it when you contact support. | | **Plan** and **Status** | Your current plan. On the free Idea plan, **Upgrade** opens billing. | | **Owner**, **Members**, **Projects** | Who owns the organization, and links to your members and projects. | | **Created** and **Last updated** | When the organization was created and last changed. | --- # Your profile and notification settings Collection: Account, team and billing URL: https://app.rectify.so/rectify/help/a/11-profile-and-notification-settings Change your name, photo and password, sign out other devices, and choose which alerts reach you. ## Your profile Select your name at the bottom of the sidebar, then **Profile**. Your profile is the same in every organization you belong to. - **Photo:** select **Upload** or **Remove**. It saves straight away. - **Display name:** the name your team sees. Select **Save changes** after you edit it. - **Email:** the address you sign in with. It can't be changed here. ![Photo, Display name and Email on the Profile page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106046038-01-profile.png) ## Change your password 1. Under **Password**, select **Change password**. 2. Enter your **Current password** and a **New password**. 3. Select **Update password**. ![2 Current and new password. 3 Update password.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106047486-02-password.png) Changing your password signs you out on every other device. ## Sign out other devices **Signed-in devices** lists the browsers and Chrome extension connections signed in to your account. Select **Sign out** on a row to end that session (**Disconnect** for an extension), or **Sign out everywhere else** to keep only the browser you're using. ## Choose your notifications Select your name at the bottom of the sidebar, then **Notifications**. These settings only change what you receive, and you set them for each organization you belong to. - **Browser push:** select **Enable** to get alerts in this browser, or **Disable** to stop them here. Each browser has its own setting. If it says **Off for this organization on all your devices**, push was turned off for the whole organization, for example in the mobile app. Select **Enable** to turn it back on. - **Email:** email alerts go to the address you sign in with. - **Alerts:** in the **Push** and **Email** tabs, switch individual alerts on or off. They start switched on, apart from four push alerts: **Member Invited**, **Role Changed**, **Workflow Completed** and **New Reaction on Changelog**. The **Push** tab works once **Browser push** is enabled in this browser. ![Channels and Alerts on the Notifications page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106049136-03-notifications.png) > **Tip:** If **Browser push** says it's blocked, click the padlock in your address bar and set Notifications to Allow, then select **Enable** again. The emails your customers receive, such as feedback confirmations, are set for each project under **Project settings**, **Email notifications**. --- # Sign in and keep your account secure Collection: Account, team and billing URL: https://app.rectify.so/rectify/help/a/12-sign-in-and-account-security The ways to sign in, how to reset a forgotten password, and how to see and sign out the devices on your account. ## Ways to sign in Sign in at [app.rectify.so/sign-in](https://app.rectify.so/sign-in) with **GitHub**, **Google**, or your email address and password. Use the same way you signed up. ![The sign-in page, with GitHub, Google and email.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106051466-01-sign-in.png) Passwords need at least 8 characters. You stay signed in as long as you use Rectify at least once every 7 days. ## Reset a forgotten password 1. On the sign-in page, select **Forgot password?**. 2. Enter the email you sign in with and select **Send reset code**. 3. Enter the 6-digit code from our email and select **Continue**. The code expires in 5 minutes. 4. Enter a **New password**, type it again under **Confirm new password**, and select **Reset password**. 5. Sign in with your new password. Signed up with GitHub or Google? You can use these steps to add a password to your account too. ## Change your password When you're signed in, change your password from your profile. [Your profile and notification settings](/rectify/help/a/11-profile-and-notification-settings) has the steps. Changing it there signs you out on every other browser and phone, and disconnects your Chrome extension and AI apps. > **Tip:** If you think someone else knows your password, change it from your profile while you're signed in. That signs out every other device straight away. ## See where you're signed in 1. Select your name at the bottom of the sidebar, then **Profile**. 2. Scroll to **Signed-in devices**. It lists your browsers, the Rectify mobile app and your Chrome extension connections. The browser you're using says **This browser**. 3. Select **Sign out** on a row to end that session, or **Disconnect** for an extension. 4. To end every other session at once, select **Sign out everywhere else** and confirm. Every other browser, phone and extension signs out, and your AI apps are disconnected. This browser stays signed in. ![Signed-in devices, and Sign out everywhere else.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106053344-02-devices.png) ## Good to know - Rectify doesn't have its own two-step verification. For a second step when you sign in, sign in with GitHub or Google and turn on two-step verification in that account. - You can't change your email address or delete your account in the app. Contact support for either. ### It says "That email and password don't match" Check you're using the email address you signed up with, or select **reset your password**. If you signed up with GitHub or Google, select that button instead. ### I didn't get a code Codes can take a minute to arrive, so check your spam folder too. Then select **Send a new code** (you can ask once a minute) and use the newest email. ### It says "Too many tries with that code" Each code allows 3 tries. Select **Send a new code** and use the code in the newest email. --- # Compare plans and what each one includes Collection: Account, team and billing URL: https://app.rectify.so/rectify/help/a/13-compare-plans Prices, seats, projects and every limit on the Idea, Build, Launch, Accelerate and Enterprise plans. Every organization has one plan. Its seats, projects and limits are shared by every project in the organization. You start on **Idea**, which is free, and every paid plan starts with a 14-day trial with no card needed. ## Prices | **Plan** | **Monthly** | **Yearly** | **Made for** | | --- | --- | --- | --- | | **Idea** | Free | Free | Trying Rectify on one project | | **Build** | $29 a month | $278 a year | A small team shipping its first product | | **Launch** | $59 a month | $566 a year | A live product under your own brand | | **Accelerate** | $99 a month | $948 a year | Teams running several products | | **Enterprise** | On request | On request | Unlimited seats, projects and monitors | Prices are in US dollars. Paying yearly saves 20%. For Enterprise, select **Contact sales** in the plan picker. ![The plans and prices on the Billing page.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106056000-01-plans.png) ## Team and projects | | **Idea** | **Build** | **Launch** | **Accelerate** | **Enterprise** | | --- | --- | --- | --- | --- | --- | | **Members** | 1 | 3 | 10 | 25 | Unlimited | | **Projects** | 1 | 3 | 10 | 25 | Unlimited | Pending invitations count as members until they're accepted or cancelled. ## Feedback, support and Help Center | | **Idea** | **Build** | **Launch** | **Accelerate** | **Enterprise** | | --- | --- | --- | --- | --- | --- | | **Support Inbox replies a month** | 10 | Unlimited | Unlimited | Unlimited | Unlimited | | **Session replays a month** | 10 | 100 | 1,000 | 5,000 | Unlimited | | **Extension sessions a month** | 10 | 100 | 1,000 | 5,000 | Unlimited | | **Annotations** | 10 | Unlimited | Unlimited | Unlimited | Unlimited | | **Console, network and action logs** | No | Yes | Yes | Yes | Yes | | **Help Center articles** | 25 | 250 | Unlimited | Unlimited | Unlimited | | **Help Center languages** | 1 | 3 | 10 | Unlimited | Unlimited | Support Inbox replies count your team's replies only. Answers from Quanta don't count. ## Analytics and monitoring | | **Idea** | **Build** | **Launch** | **Accelerate** | **Enterprise** | | --- | --- | --- | --- | --- | --- | | **Analytics events a month** | No | 500,000 | 2 million | 10 million | Unlimited | | **Analytics history** | No | 90 days | 180 days | 1 year | 2 years | | **Uptime monitors** | 1 | 3 | 10 | 25 | Unlimited | | **Uptime check interval** | 10 minutes | 5 minutes | 1 minute | 1 minute | 1 minute | | **Alert channels** | 1 | 3 | 5 | 10 | Unlimited | | **Phone and SMS alerts** | No | No | Yes | Yes | Yes | | **SSL and domain expiry checks** | No | Yes | Yes | Yes | Yes | | **Maintenance windows** | No | Yes | Yes | Yes | Yes | ## Messaging, development and AI | | **Idea** | **Build** | **Launch** | **Accelerate** | **Enterprise** | | --- | --- | --- | --- | --- | --- | | **Subject line tests** | No | No | Yes | Yes | Yes | | **Send in each person's time zone** | No | No | Yes | Yes | Yes | | **Code scans a month** | No | 10 | 25 | 100 | Unlimited | | **MCP server** | No | Yes | Yes | Yes | Yes | | **AI credits** | No | $5 | $10 | $15 | Custom | | **Claude, OpenAI, OpenRouter and Kimi keys** | No | Yes | Yes | Yes | Yes | AI credits let Quanta and the other AI features run without your own key. They're a one-time amount, not a monthly one. When they run out, connect your own provider under **Organization settings**, **AI providers**. On Idea, connect a Gemini or Deepseek key to use AI features. ## Branding and domain | | **Idea** | **Build** | **Launch** | **Accelerate** | **Enterprise** | | --- | --- | --- | --- | --- | --- | | **Custom domain** | No | No | Yes | Yes | Yes | | **Remove Rectify branding** | No | No | Yes | Yes | Yes | ## See your own limits Open **Organization settings**, then **Billing**. Owners and Admins see the current plan and what's used, and **View all limits** shows the full list. When you reach a limit, Rectify tells you and suggests a plan with more room. [Upgrade, change or cancel your plan](/rectify/help/a/14-upgrade-change-or-cancel-your-plan) explains how to move up. --- # Upgrade, change or cancel your plan Collection: Account, team and billing URL: https://app.rectify.so/rectify/help/a/14-upgrade-change-or-cancel-your-plan Start a free trial, upgrade, switch between monthly and yearly billing, or cancel, from the Billing page. > **Note:** **Before you start.** Only Owners and Admins can change the plan. A Member who opens an upgrade prompt can select **Copy upgrade link** and send it to one of them. ## Start a trial or upgrade 1. Open **Organization settings**, then **Billing**. 2. Choose **Monthly** or **Yearly**. Yearly saves 20%. 3. Pick a plan. **What changes on** the plan lists what you'll get, and **All limits** shows everything. 4. Select the trial button, for example **Start 14-day Launch trial**. No card is needed. ![2 Monthly or Yearly. 3 Pick a plan. 4 Start the trial.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106058665-01-choose-plan.png) To pay straight away instead, select **Skip the trial and pay** under the trial button. Checkout opens next, where you pay by card. Prices are in US dollars. Upgrade prompts in the app, for example when you reach a limit, open the same plan picker. ## Change your plan or billing on a paid plan 1. Open **Organization settings**, then **Billing**. 2. Under **Change plan**, select the pencil next to **Plan** or **Billing interval**, and pick the new one. 3. Select **Update subscription**, then **Update** to confirm. You're charged or credited the difference straight away. To move to a smaller plan, you need to fit its limits first. If you have more members or projects than it allows, you'll see a message starting "Cannot downgrade". Remove members or projects, then try again. ## Cancel your subscription 1. Open **Organization settings**, then **Billing**. 2. Select **Cancel subscription**. 3. Type `CANCEL` to confirm, then select **Cancel Subscription**. Your paid features stay on until the end of the billing period you've paid for. After that, your organization moves to the free **Idea** plan. Changed your mind before then? On **Billing**, select **Reactivate subscription**, then **Reactivate**. Your plan carries on, and the next billing period is charged as usual. Once the subscription has ended, select **Choose a plan** on **Billing** to pick a plan again. ## Enterprise For unlimited seats, projects and monitors, pick **Enterprise** in the plan picker and select **Contact sales**. ### I can't open Billing Only Owners and Admins can see Billing. Ask one of them to change the plan for you. [Compare plans and what each one includes](/rectify/help/a/13-compare-plans) lists the limits on every plan. --- # Earn rewards Collection: Account, team and billing URL: https://app.rectify.so/rectify/help/a/15-earn-rewards Review Rectify or share it, send us proof, and get extra team members and projects for your organization. > **Note:** **Before you start.** Everyone in an organization can open Rewards, whatever their role and plan. Rewards go to the organization you have selected, not to you personally. Rewards give your organization extra room on top of your plan, in return for reviewing or sharing Rectify. ## Open Rewards 1. Select your name at the bottom of the sidebar. 2. Select **Rewards**. ![1 Your name. 2 Rewards.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106061185-01-menu.png) ## What you can earn The page groups the tasks by what they earn. The number next to each task is what it adds. | **Section** | **Task** | **Reward** | | --- | --- | --- | | **Team members** | **Leave a review on Earlybird** | +3 | | **Team members** | **Leave a review on Product Hunt** | +3 | | **Projects** | **Create a social media post** | +3 | | **Organizations** | **Leave a review on G2** | +1 | | **Organizations** | **Create a review video** (3 minutes or longer) | +1 | ![The tasks, with Get Started on review tasks and Submit Proof on the others.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106063074-02-tasks.png) **Team members** and **Projects** show how many you've earned so far, for example **0 of 6 earned**. Together the tasks can earn up to 6 team members and 3 projects. ## Complete a task and send proof 1. On a review task, select **Get Started**. The review page opens in a new tab. 2. Write your review, or make your post or video. 3. Take a screenshot of your approved review or your post. For a video, copy its link. 4. Back on Rewards, select **Submit Proof**. It's at the top of the page and on the social post and video tasks. 5. In the form that opens, add your screenshot or link, and send it. Include your organization's name so we add the reward to the right one. ## How rewards are checked - We check each proof by hand and add the reward within 1 to 5 business days. - A G2 review only counts once G2 has approved it. - Follow each platform's own guidelines, or the submission won't count. ![How to Redeem, with the note about G2 reviews.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106064740-03-redeem.png) ## What rewards add - **Team members** add seats on top of your plan's, so you can invite more people. - **Projects** add room for more projects on top of your plan's. Rewards stay with your organization when you change plans. On a plan that's already unlimited, like Enterprise, they don't change anything. To check what you've received, Owners and Admins can open **Organization settings**, then **Billing**. Under **Usage**, **Members** and **Projects** then say, for example, "3 on your plan plus 3 from rewards." Under **View all limits**, a feature unlocked through a reward, like **Remove Branding**, has a gift icon that says **Unlocked via rewards**. ## Troubleshooting ### Nothing opens when I select Submit Proof The form opens in Rectify's own widget, which loads with the page. Reload the page and try again. ### I sent proof but don't see the reward yet Rewards are added by hand within 1 to 5 business days, and a G2 review only counts once G2 approves it. Check **Billing** after that, or ask an Owner or Admin to check. ## Read next - [Compare plans and what each one includes](/rectify/help/a/13-compare-plans) - [Invite your team](/rectify/help/a/6-invite-your-team) --- # Set a monthly spend limit on your AI keys Collection: Account, team and billing URL: https://app.rectify.so/rectify/help/a/16-set-a-spend-limit-on-your-ai-keys Cap how much Rectify spends each month on each AI provider key you connect, and see what happens when a limit is reached. > **Note:** **Before you start.** Owners and Admins can change AI providers. A spend limit applies to your own provider keys. Rectify credits are a fixed amount, so they don't need one. ## Set a limit 1. Open **Organization settings**, then **AI providers**. 2. Select a provider to open it, for example **Claude**. 3. Under **Monthly spend limit**, enter an amount in US dollars. It must be at least $5. Leave it empty for no limit. 4. Select **Save changes**. If you're connecting the key for the first time, select **Connect** instead. ![3 Monthly spend limit. 4 Save or connect.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106067286-01-spend-limit.png) Each provider has its own limit. A new key has no limit until you set one. ## What happens near and at the limit Rectify estimates what each key has spent this month from the tokens it used and the model's price. The month runs on the calendar, in UTC. - **At 80%**, we email the person who set up AI providers for your organization. - **At 100%**, we email again and stop using that key until next month. AI features switch to your other providers, then to your Rectify credits. - If nothing else is left, AI features stop and show a message that the month's spend limit is reached. To start again straight away, raise the limit or leave it empty, then save. > **Important:** Reading images, PDFs and screenshots, making images, changelog covers and phone calls run on Gemini only. When your Gemini key reaches its limit, those features stop until next month, even if you have other keys. Your provider's own bill can differ a little from our estimate. To be sure you never pay more than you plan for, set a limit in your provider's account too. ## Rectify credits Paid plans include Rectify credits, so AI features work before you connect a key: $5 on Build, $10 on Launch and $15 on Accelerate. Credits are a one-time amount, not a monthly one. The **Rectify credits** card at the top of **AI providers** shows what's left. When they're used up, connect a provider to keep AI features running. [Meet Quanta, your AI teammate](/rectify/help/a/7-meet-quanta) explains what Quanta does with these keys. --- # Archive or delete a project Collection: Account, team and billing URL: https://app.rectify.so/rectify/help/a/17-archive-or-delete-a-project Tidy away a project you no longer use, or delete it and everything in it for good. > **Note:** **Before you start.** Anyone who can open a project can archive it. Only the organization's Owner can delete a project. ## Archive a project Archiving moves a project out of your project switcher. Everything in it is kept. 1. Open **Projects**: select the Rectify logo at the top of the sidebar, or **All projects** in the project switcher. 2. On the project's card, open the menu (⋮). 3. Select **Archive**. 4. Select **Archive** again to confirm. ![2 The project's menu. 3 Archive.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106070126-01-menu.png) The card now shows **Archived**, and you'll find it under the **Archived** tab on **Projects**. You can still open it from there. > **Important:** Archiving doesn't switch anything off. The project's portal, widget and monitors keep running, and it still counts toward the projects on your plan. You can't unarchive a project from the app. ## Delete a project Deleting a project removes it and everything in it, for good. That includes feedback, session replays, conversations, the roadmap, changelog, portal, help center, widget, monitors, contacts, analytics, Quanta chats and uploaded files. 1. Open **Projects**. 2. On the project's card, open the menu (⋮) and select **Delete**. 3. Type the project's name. 4. Select **Delete**. ![3 Type the project's name. 4 Delete.](https://replicate-assets.s3.eu-west-2.amazonaws.com/projects/67cb1ec0f47ea9a75e660715/help-center-contents/1793106071745-02-delete.png) Most of the project goes straight away. Uploaded files and other large data are cleared in the background within the next hour. The project, its monitors and its published help articles stop counting toward your plan as soon as you delete it. > **Warning:** Deleting a project can't be undone. If you might need it again, archive it instead. ### I can't select Delete Only the organization's Owner can delete a project. Admins and Members see **Delete** greyed out, so ask your Owner. ### I only want to rename the project Select **Edit** in the same menu. You can change the project's logo, name, description, website and colour there.