Skip to content
Feply
Better First Replies
Log inStart free trial
Support

Search the Feply help center before you open a ticket.

Ask your question in plain language and Feply will match it to the most relevant support answers for dashboard sync, automation runs, AI steering, pipeline, billing, trials, and team access.

We use AI models and can make mistakes
Powered by A.I.
Start here
First check

Refresh the Feply dashboard, confirm the extension is enabled in the same Chrome profile, and reload the active Thumbtack tab.

Before support

Gather the workspace, page, plan, exact issue, and screenshot so support can understand the problem faster.

Need human help?

If you already tried the guide that matches your issue, open a support request with screenshots, exact timing, workspace, and the action that failed.

Contact support
To reopen an existing public ticket, use the secure link in the support email. That email contains the access token required to view the conversation.
Coverage

Sync, extension connection, automation run controls, AI steering, pipeline workflows, billing, trials, seats, invites, and how-to guidance.

Built for mobile

Search, quick paths, and article containers are stacked for smaller screens so users can troubleshoot without leaving the page.

Results

33 support articles available across 8 sections.

Connecting Feply to the dashboard and extensionTroubleshooting run, start, and stop issuesMobile automation sync and Add to Home setupAI Steering Pool, Analytics, and reply-quality guidesPipeline visibility, stages, and activity trackingPayments, checkout, plan changes, trials, and seat billingSeats, invites, roles, workspaces, and permissionsPractical setup and operating guides
Setup & Sync

Connecting Feply to the dashboard and extension

Use these guides when the extension is installed but the dashboard cannot see it, sync appears stale, or capabilities are missing.

Dashboard says Feply is not connected

Fix the most common reasons the dashboard cannot detect the Chrome extension or current browser session.

Open
When this article applies
  • The dashboard shows that automation controls are unavailable or disconnected.
  • The extension appears installed, but Feply still asks you to connect it.
  • You changed accounts, browsers, or profiles and the dashboard stopped seeing the extension.
Recommended steps
  1. 1Open Chrome's extension manager and confirm Thumbtack Lead Drafter is enabled in the same browser profile you use for Feply.
  2. 2Reload the Feply dashboard tab after enabling or updating the extension so the dashboard bridge can re-register.
  3. 3Make sure the Feply tab is on the production domain and not an old preview URL, incognito window, or unsupported browser.
  4. 4Sign out of Feply, sign back in, and let the dashboard refresh entitlements and workspace permissions.
  5. 5If the issue started right after an extension update, remove the old build and reload the newest package so the service worker restarts cleanly.
Helpful notes
  • If the extension connects on one Chrome profile but not another, the issue is usually profile-specific permissions or an outdated build.
  • If you use a work-managed device, check whether Chrome extensions and background activity are restricted.
Extension looks connected, but settings or entitlements are stale

Refresh extension state when billing changes, debug visibility, or automation permissions do not match the dashboard.

Open
When this article applies
  • You upgraded plans but the extension still behaves like the old tier.
  • Debug controls or automation capabilities appear missing after an account change.
  • Workspace access changed and the extension did not catch up.
Recommended steps
  1. 1Refresh the dashboard and leave it open for a few seconds so the extension can receive the latest account and capability payload.
  2. 2Open the extension options or popup if available, then return to the dashboard to prompt a fresh background sync.
  3. 3If the workspace was switched, confirm you are in the correct workspace inside Feply before retrying automation.
  4. 4Close Thumbtack tabs and reopen them so content scripts load with the latest extension context.
  5. 5If billing or role changes happened moments ago, wait briefly and refresh once more before contacting support.
Thumbtack tab is open, but Feply still says automation is unavailable

Verify that the extension is active on the right page and that Thumbtack content scripts are running.

Open
When this article applies
  • Automation controls stay disabled even though Thumbtack is open.
  • The extension icon is present, but the lead drafter panel never appears.
  • Reloading the dashboard alone does not fix the issue.
Recommended steps
  1. 1Open an actual Thumbtack leads or messaging page, not just the general Thumbtack home screen.
  2. 2Reload the Thumbtack tab so the extension content script can attach to the live page.
  3. 3Avoid duplicate Thumbtack sessions in multiple profiles if one of them is signed out or stale.
  4. 4If the page layout changed or partially loaded, fully refresh Thumbtack before retrying run, start, or stop actions from the dashboard.
  5. 5Confirm that no aggressive ad blocker or script blocker is preventing the extension from injecting page controls.
How to reopen a support ticket from email

Use the secure ticket link correctly if you contacted Feply without a member account.

Open
When this article applies
  • You received a support email but are unsure where to reply.
  • The support page does not show your ticket automatically.
  • You opened `/support` directly and expected to see the full conversation.
Recommended steps
  1. 1Use the secure link in the support email because it contains the token needed to open that conversation.
  2. 2If the link expired or was forwarded, go to contact and ask support to resend the latest access link.
  3. 3Reply from the same email address used in the original request so support can match the case faster.
Automation

Troubleshooting run, start, and stop issues

Use these articles when automation will not launch, stops unexpectedly, or behaves differently between dashboard and Thumbtack tabs.

Run now is clicked but nothing happens

Resolve the common blockers that prevent a one-time automation run from firing.

Open
When this article applies
  • You click Run now and the button returns to idle with no visible result.
  • The dashboard shows a short error and the Thumbtack tab never changes.
  • The issue happens intermittently after inactivity.
Recommended steps
  1. 1Refresh the dashboard first, because dashboard control grants are short-lived and must be current when you click the action.
  2. 2Confirm the connected workspace still has permission to run automation for the current plan and user role.
  3. 3Bring the active Thumbtack tab to the foreground and make sure it is fully loaded before retrying.
  4. 4If the browser was asleep or resumed from standby, refresh both Feply and Thumbtack to re-establish the bridge.
  5. 5Try a single manual run before using continuous automation so you can isolate whether the issue is page readiness or long-running state.
Helpful notes
  • If the dashboard reports that controls are not allowed from the current page, the tab is usually not on the supported dashboard path or the extension needs a fresh reload.
  • If Run now only fails after long idle periods, a simple dashboard refresh usually fixes expired run authorization.
Continuous automation started, then stopped unexpectedly

Stabilize long-running sessions when automation pauses after page changes, navigation, or browser sleep.

Open
When this article applies
  • Continuous automation starts successfully and then goes idle.
  • Thumbtack navigated away from the expected screen or refreshed mid-run.
  • The browser machine slept or the tab became resource constrained.
Recommended steps
  1. 1Keep the supported Thumbtack page open and avoid navigating to unrelated views while automation is running.
  2. 2Disable Chrome tab sleeping or memory saver for the Feply and Thumbtack tabs if your machine aggressively suspends them.
  3. 3If you run multiple workspaces, confirm the run session belongs to the same workspace shown in the dashboard.
  4. 4Restart with a fresh Start command from the dashboard instead of repeatedly pressing Run now after a stop.
  5. 5If the stop followed a visible page error or empty state, reload Thumbtack and restart from a known-good page.
How dry-run, review, and auto-send settings affect behavior

Understand why automation may draft correctly but not send, or why it appears slower than expected.

Open
When this article applies
  • Replies are drafted but not sent.
  • Automation pauses for review even though you expected hands-off behavior.
  • Different teammates see different automation outcomes.
Recommended steps
  1. 1Open workspace automation settings and check whether dry-run mode is enabled.
  2. 2Confirm the workflow is configured for review-before-send versus optional auto-send first reply.
  3. 3Review any safety or approval requirements added at the team or workspace level.
  4. 4If only some users can auto-send, verify plan entitlements and role-based controls for that workspace.
  5. 5Test with one fresh lead after saving settings so you can confirm the exact behavior end to end.
Automation works on some leads but not others

Identify when the lead page itself, missing data, or unsupported state causes inconsistent automation results.

Open
When this article applies
  • One lead drafts correctly while the next one does not.
  • Only certain categories or lead pages fail.
  • The extension panel shows less information on some leads.
Recommended steps
  1. 1Check whether the lead contains enough structured details for the current prompt and reply rules to operate well.
  2. 2Avoid running on archived, already-replied, or partially rendered lead pages.
  3. 3Refresh the lead and wait for all message and customer details to finish loading before retrying.
  4. 4If one lead repeatedly fails, capture a screenshot and open a support request with the exact lead state and expected behavior.
Mobile & Home Screen

Mobile automation sync and Add to Home setup

Use these guides when mobile automation status looks stale, desktop changes are not showing up on your phone, or you want Feply on your home screen like an app.

Mobile automation controls are not syncing with desktop

Stabilize cross-device automation when status, mode, or settings changes lag between the phone dashboard and the connected desktop extension.

Open
When this article applies
  • Switching between Test and Live on mobile updates the desktop controls, but automation settings or status do not refresh consistently in the other direction.
  • Desktop or mobile shows older review timer, mode, or safety settings until you refresh the page.
  • Processed counts, sync badges, or extension connection status look delayed on one device.
Recommended steps
  1. 1Open the Automation page on both devices and leave each page visible for a few seconds so the dashboard can poll the latest workspace settings revision and remote runtime heartbeat.
  2. 2Save settings changes once, then pause briefly instead of tapping multiple times. Feply now queues remote config refresh safely, but repeated taps can still make troubleshooting harder.
  3. 3Keep the connected desktop browser and Thumbtack tab awake. If the desktop browser sleeps, background sync and remote runtime heartbeats can go stale until that browser is active again.
  4. 4If one device still looks stale after a short wait, navigate away from Automation and back again. The page will fetch fresh settings and runtime state on route entry without requiring a hard refresh.
  5. 5If status still disagrees, reload the desktop extension build and reopen the Automation page so the connected extension session can publish a fresh heartbeat and apply the newest settings revision.
Helpful notes
  • Automation settings are designed to apply on the next safe automation cycle, so a currently processing lead may finish before the newest settings take over.
  • If the mobile dashboard can start, stop, or switch modes but counts look behind, wait for the next heartbeat before assuming the command failed.
Add Feply to Home Screen on iPhone or iPad

Use Safari's Add to Home Screen flow to launch Feply like an app even though there is no App Store download yet.

Open
When this article applies
  • You searched the App Store and could not find an official Feply app.
  • You want faster mobile access without opening Safari and typing the site each time.
  • You want the dashboard to open in a cleaner home-screen experience on iPhone or iPad.
Recommended steps
  1. 1Open Feply in Safari on your iPhone or iPad. Safari is the supported browser for Add to Home on Apple devices.
  2. 2Tap the Share button, then choose Add to Home Screen.
  3. 3Edit the shortcut name if you want, then tap Add.
  4. 4Open Feply from the new home-screen icon and sign in as usual to reach the dashboard quickly.
  5. 5If you already had an older shortcut, remove it and add the latest one again so the icon and standalone launch metadata stay current.
Helpful notes
  • Feply currently uses Add to Home instead of a native App Store app.
  • The installed home-screen experience still needs network access and your normal account session.
Add Feply to Home Screen on Android

Install Feply from Chrome's Add to Home or Install prompt so Android users can launch it like an app without Play Store distribution.

Open
When this article applies
  • You searched the Play Store and could not find an official Feply app.
  • You want one-tap dashboard access from your Android home screen.
  • You want the site to open in a more app-like window on your phone.
Recommended steps
  1. 1Open Feply in Chrome on Android.
  2. 2Use Chrome's Add to Home Screen or Install option from the browser menu when it appears.
  3. 3Confirm the install so Feply is added to your home screen.
  4. 4Launch Feply from the new icon and sign in as usual.
  5. 5If Chrome shows an older shortcut or stale icon, remove it and install the current home-screen version again.
Helpful notes
  • Feply currently uses Add to Home instead of a native Play Store app.
  • The installed home-screen experience is still the live web app, so it requires network access.
AI & Guidance

AI Steering Pool, Analytics, and reply-quality guides

Use these guides when replies feel off-brand, steering changes do not take effect, or questions seem weaker than expected.

AI Steering Pool changes are not showing up in replies

Refresh the right inputs when new steering guidance or tone rules seem ignored.

Open
When this article applies
  • You changed steering guidance, but new drafts still sound like the old version.
  • Only some replies appear to reflect the updated instructions.
  • The dashboard saved your changes, but the extension output did not improve.
Recommended steps
  1. 1Save the guidance changes and run a fresh draft on a newly loaded lead rather than relying on an already-open draft.
  2. 2Refresh the dashboard after large prompt or profile changes so extension context is renewed.
  3. 3Confirm the changes were made in the correct workspace if you manage multiple brands or teams.
  4. 4Simplify conflicting rules so high-priority tone, service, and CTA guidance do not compete with one another.
  5. 5Compare one before-and-after draft to verify whether the change affected intros, questions, or closing language.
Helpful notes
  • If guidance was pasted from a rich-text source, remove unusual formatting and keep instructions direct, short, and explicit.
  • If multiple teammates edit guidance, choose one person to make final updates so your instructions stay consistent.
Analytics suggestions feel generic or repetitive

Improve output quality by strengthening business context, service specifics, and boundaries for the model.

Open
When this article applies
  • Replies sound safe but not differentiated.
  • Questions are too broad or fail to move the conversation forward.
  • Drafts miss your preferred style, pricing framing, or service priorities.
Recommended steps
  1. 1Expand your business profile with clearer service scope, differentiators, and preferred next-step language.
  2. 2Add examples of good replies or successful question patterns to your templates and guidance.
  3. 3Reduce vague instructions such as 'sound professional' and replace them with specific tone and CTA rules.
  4. 4Review whether the lead itself has enough detail to support a stronger question or estimate-oriented reply.
  5. 5Use a small set of high-value instructions rather than a long stack of overlapping rules.
How Feply uses lead text and photos in first replies

Understand what Feply extracts from the lead page so teams can explain the workflow clearly to customers and staff.

Open
When this article applies
  • A customer asks whether Feply reads attached lead photos.
  • A teammate assumes the draft only uses typed lead text.
  • You want to explain when Feply asks the lead to send photos.
Recommended steps
  1. 1Treat the lead's typed request and Thumbtack question answers as the primary source of truth for the draft.
  2. 2If photos are attached, Feply can analyze them for useful visual scope cues such as visible condition, finish, damage pattern, or job complexity.
  3. 3If no photos are attached and the business profile is set to ask for photos only when missing, the draft can ask the lead to share photos when that would help scope or quote the work.
  4. 4Review the generated draft before send if you want to confirm how the photo context was incorporated.
Helpful notes
  • Photo analysis supports the written lead details instead of replacing them.
  • The pipeline can surface how many photos were reviewed by AI and any saved visual observation summary.
Replies do not sound like the business brand

Reinforce voice, service framing, and sign-off behavior so drafts match the company more consistently.

Open
When this article applies
  • Drafts feel too formal, too casual, or too pushy.
  • Business name, sign-off, or service language is inconsistent.
  • One teammate's edits changed the style for everyone else.
Recommended steps
  1. 1Update the workspace profile, footer, and sign-off settings with the exact phrases you want repeated consistently.
  2. 2Add one or two model examples of ideal responses instead of describing the style in abstract terms.
  3. 3Audit templates and prompt governance so old copy is not reintroducing the wrong voice.
  4. 4If you are on Team, centralize brand instructions and ask responders not to maintain conflicting private guidance.
Lead questions are too weak or not moving prospects forward

Tighten discovery logic when the AI asks questions that fail to qualify or convert.

Open
When this article applies
  • Prospects answer vaguely or stop responding.
  • Questions repeat information already on the lead.
  • The reply feels longer than necessary without creating momentum.
Recommended steps
  1. 1Prioritize one or two high-leverage questions tied to scheduling, scope, urgency, or budget fit.
  2. 2Avoid stacking too many questions in the first response if the lead already contains detailed notes.
  3. 3Add guidance telling Feply when to confirm details versus when to advance to a call or estimate step.
  4. 4Review successful booked-job conversations and feed those patterns back into templates or steering.
Pipeline

Pipeline visibility, stages, and activity tracking

Find fixes for missing stages, stale run history, activity gaps, and workflow visibility problems.

Pipeline is not updating after replies or runs

Resolve lag or missing state changes when the pipeline appears behind actual lead activity.

Open
When this article applies
  • A reply was drafted or sent, but the pipeline did not change.
  • Run history looks incomplete compared with what happened in the tab.
  • The dashboard looks stale after a long session.
Recommended steps
  1. 1Refresh the dashboard first to pull the latest activity and pipeline state.
  2. 2Confirm the run completed successfully rather than stopping on a lead or page error mid-flow.
  3. 3If several teammates worked the same workspace, ask them to refresh too so everyone sees the same latest state.
  4. 4Retry on one fresh lead and compare whether that new activity is captured correctly.
  5. 5If history is still missing, send support the workspace, approximate time, and action taken so the team can inspect logs.
Leads are appearing in the wrong stage

Use this guide when a lead appears in a different stage than you expected.

Open
When this article applies
  • A lead looks active but shows in a stage your team does not use for that scenario.
  • Different teammates interpret the same stage differently.
  • A custom process changed, but the team still expects the old mapping.
Recommended steps
  1. 1Review how your team defines each pipeline stage so everyone is working from the same expectations.
  2. 2Check whether the underlying lead action was draft-only, sent, paused, or manually handled outside the standard flow.
  3. 3If your process recently changed, update team playbooks and prompt governance so stage transitions stay aligned.
  4. 4Capture a before-and-after screenshot if one specific state repeatedly lands in the wrong stage.
Run history or activity logs are incomplete

Use this guide when you expect to see an activity entry but it has not appeared in the dashboard yet.

Open
When this article applies
  • A responder says they took action, but the dashboard does not show it.
  • Team members disagree on whether automation ran.
  • You need exact timestamps for billing or troubleshooting.
Recommended steps
  1. 1Refresh the dashboard and reopen the relevant page section first.
  2. 2Check whether the action was performed under the same workspace and user you are currently reviewing.
  3. 3If the activity was manual outside the normal automation path, note that it may not appear in the same history stream.
  4. 4For audit questions, record the lead, workspace, and approximate timestamp before opening a support request.
How to use the pipeline effectively

A practical guide for teams that want the pipeline to become part of their daily workflow instead of a passive report.

Open
When this article applies
  • Your team has pipeline access but is not sure how to use it day to day.
  • Stages are visible, but nobody is acting from them consistently.
  • Managers want better accountability across responders.
Recommended steps
  1. 1Define which stages require action today versus which are informational only.
  2. 2Use run history and activity logs during daily reviews so the team sees pipeline movement tied to actual work.
  3. 3Assign a clear person for each follow-up stage so leads do not sit without a next step.
  4. 4Review stage aging weekly and refine prompts or rules where leads repeatedly stall.
Billing & Trials

Payments, checkout, plan changes, trials, and seat billing

Handle card failures, plan confusion, yearly versus monthly questions, and trial-to-paid issues from one place.

Payment is not processing at checkout

Troubleshoot the most common checkout blockers before contacting support.

Open
When this article applies
  • Checkout fails before the subscription starts.
  • The card form submits but returns an error.
  • You switched plans or intervals and checkout started failing.
Recommended steps
  1. 1Confirm the selected plan and interval are the ones you intended before resubmitting payment.
  2. 2Retry in the same browser session first, then refresh once and submit again to clear stale checkout state.
  3. 3Check whether the card issuer blocked the payment, especially on first-time business subscriptions or large annual charges.
  4. 4Avoid multiple rapid retries if the same error repeats, because that can trigger fraud protections.
  5. 5If the page mentions billing configuration mismatch, stop and contact support instead of forcing more checkout attempts.
Helpful notes
  • Annual charges are larger single transactions, so cards that pass monthly charges may still require issuer approval for yearly billing.
  • If your card succeeds elsewhere but not in Feply, capture the exact wording of the checkout error for support.
Trial did not start or ended sooner than expected

Understand how trial enrollment works and what to verify if the workspace moved to paid unexpectedly.

Open
When this article applies
  • You signed up expecting a trial but landed in paid billing.
  • The dashboard indicates the trial has expired earlier than expected.
  • A second signup behaved differently from the first.
Recommended steps
  1. 1Check whether the workspace already had a prior subscription or trial history under the same account or billing identity.
  2. 2Confirm you completed signup on the intended plan and interval.
  3. 3Review billing status in the dashboard to see whether the workspace is trialing, active, or incomplete.
  4. 4If you are unsure which workspace the trial belongs to, verify the current workspace in the dashboard before contacting support.
How monthly and yearly billing work

Know what changes when you toggle billing cadence and how that affects plan price displays and renewal behavior.

Open
When this article applies
  • The pricing page shows different totals than expected.
  • You want to understand whether yearly billing changes seat pricing or renewal timing.
  • A teammate selected the wrong cadence at checkout.
Recommended steps
  1. 1Use the pricing toggle before checkout to verify the intended billing interval.
  2. 2Check the displayed plan note, especially for Team, because seat pricing differs between monthly and yearly billing.
  3. 3Review your checkout summary before paying and confirm the interval shown there matches your intent.
  4. 4If you already subscribed on the wrong cadence, contact support before making repeated plan changes.
How to pause a subscription for 30, 60, or 90 days

Use this when a customer asks whether pausing is supported, how long a pause can last, or where to manage it.

Open
When this article applies
  • You want a temporary billing break instead of canceling the subscription.
  • You were told there is no pause option and want to confirm whether it exists.
  • You want to know the maximum pause length or whether the subscription can resume early.
Recommended steps
  1. 1Open Billing in the dashboard and use the Pause subscription action there.
  2. 2Choose one of the current pause lengths: 30, 60, or 90 days.
  3. 3Know that the pause is scheduled for the next billing cycle rather than taking effect immediately mid-cycle.
  4. 4Resume earlier from Billing if you want the subscription to restart before the scheduled pause end date.
Helpful notes
  • Customers can pause for up to 90 days total.
  • If nothing is changed before the pause ends, the subscription and any active add-ons cancel automatically.
Refunds, failed renewals, and billing help

Use this path when the subscription already exists and billing support is needed after purchase.

Open
When this article applies
  • A renewal failed and features may be restricted.
  • You need invoice or receipt help.
  • You want to review refund policy or ask about a recent charge.
Recommended steps
  1. 1Review the billing section inside the dashboard first to confirm the active plan and workspace status.
  2. 2Use the refund policy for policy details, then contact support with the workspace, charge date, and issue summary.
  3. 3If the payment method failed, update the saved card before retrying plan or seat changes.
Team & Access

Seats, invites, roles, workspaces, and permissions

Use these guides for adding seats, inviting teammates, switching workspaces, and understanding role-based access.

How to add seats on Team

A practical guide for increasing capacity when the included seats are no longer enough.

Open
When this article applies
  • You are trying to invite another teammate and the workspace has no remaining included seats.
  • The team invite flow warns that paid capacity must be added first.
  • You want to know how extra seat billing works.
Recommended steps
  1. 1Open Team Access or Billing in the dashboard and start the seat purchase flow from there.
  2. 2Review the displayed rate for the current billing interval before confirming purchase.
  3. 3After the seat capacity is added, resend or continue the invite so the teammate can join.
  4. 4Keep track of the workspace's active billing interval because monthly and yearly extra seat pricing differ.
How to use Team roles correctly

Understand which roles should manage billing, responders, analytics, and shared settings.

Open
When this article applies
  • A teammate can see too much or too little.
  • Billing or workflow changes are blocked for some users.
  • Your team is unsure which role fits each person.
Recommended steps
  1. 1Assign the narrowest role that still lets the teammate do their job.
  2. 2Use higher-access roles for billing and shared workflow control only when necessary.
  3. 3If a responder only needs operational access, avoid granting broader billing or admin privileges.
  4. 4Review role assignments periodically after staffing changes or process changes.
Team invite email did not arrive or cannot be accepted

Fix the most common issues with teammate acceptance links and delivery.

Open
When this article applies
  • A teammate never received the invite email.
  • The acceptance link opens but fails or looks expired.
  • The teammate is trying to accept with the wrong email address.
Recommended steps
  1. 1Confirm the invite was sent to the correct email and check spam or security filtering.
  2. 2Ask the teammate to open the latest invite email because older links may no longer be valid.
  3. 3Make sure the teammate accepts the invite with the same email address that was invited.
  4. 4If necessary, revoke and resend the invite rather than trying to reuse a questionable link.
Workspace access or multi-workspace control is not behaving as expected

Troubleshoot workspace-switching issues for Team accounts managing multiple brands or pros.

Open
When this article applies
  • The user can sign in but cannot access the expected workspace.
  • The extension seems tied to a different workspace than the dashboard.
  • A manager expects up to 5 workspaces but cannot see them all.
Recommended steps
  1. 1Check which workspace is active in the dashboard before reviewing automation, pipeline, or billing behavior.
  2. 2Confirm the user's role on that workspace rather than assuming access is global across the account.
  3. 3If the extension and dashboard appear mismatched, refresh the dashboard and reopen the relevant Thumbtack tab so both contexts sync to the same workspace.
  4. 4If you should have access but do not, ask the person who manages your workspace access to review your assignment.
How-To

Practical setup and operating guides

A guided starting point for teams that want to set up Feply correctly, train responders, and avoid the most common issues.

How to launch automation safely for a new workspace

A recommended rollout path that protects quality while getting value quickly.

Open
When this article applies
  • You are new to Feply and want the safest way to go live.
  • The team wants to avoid auto-send mistakes during onboarding.
  • You want a checklist for first-week setup.
Recommended steps
  1. 1Start with the business profile, footer, and sign-off settings so the AI has correct baseline context.
  2. 2Run in draft or dry-run mode first and review several real replies before enabling higher automation.
  3. 3Tune steering guidance using actual leads from your service mix, not hypothetical examples only.
  4. 4Once replies are consistent, enable the workflow level that fits your team's review tolerance.
  5. 5Use pipeline and activity history in the first week to catch friction early and retrain the team.
How to improve reply quality quickly

A short playbook for turning average first drafts into consistently useful messages.

Open
When this article applies
  • The system is working technically, but the output is not strong enough.
  • Your team wants better openings, questions, and next steps.
  • You want a simple optimization routine.
Recommended steps
  1. 1Collect 5 to 10 strong real replies and identify repeated patterns that book calls or jobs.
  2. 2Update your steering guidance with those patterns using concrete instructions and examples.
  3. 3Refine one variable at a time, such as greeting style, question strategy, or closing CTA.
  4. 4Review results in live leads instead of only evaluating the copy in isolation.
How to train a team on Feply

A simple setup guide for teams with managers and responders.

Open
When this article applies
  • New teammates are joining and need a consistent process.
  • Different responders are using the product differently.
  • Managers want predictable QA and accountability.
Recommended steps
  1. 1Teach responders where to review pipeline, run history, and support before they begin handling leads.
  2. 2Standardize who updates guidance, billing changes, and workflow approvals.
  3. 3Use one short training session for live lead review so teammates can see what a strong assisted reply looks like.
  4. 4Set clear team rules for when to use manual review and when to contact support.
When to self-serve versus when to contact support

Use the help center first for common setup and workflow issues, then contact support with the right details if you still need help.

Open
When this article applies
  • You are not sure whether the issue is configuration or a product bug.
  • A teammate wants to send a vague support request without useful details.
  • You want faster resolution if support does need to step in.
Recommended steps
  1. 1Use the relevant article here first for sync, automation, billing, pipeline, or seat-management issues.
  2. 2If the issue persists, gather the workspace, user role, plan, exact page, timestamp, and what you expected to happen.
  3. 3Include screenshots or photos when the problem is visual or tied to a specific lead state.
  4. 4Open the contact form or dashboard support request with those details so support can help faster.
Need more help?

Still stuck after following the guide?

Send support the workspace name, exact page, what action you took, what you expected to happen, what happened instead, and screenshots. That gives the team the details needed to help you faster.

Open contact formReview billing and refund policy