Revenue Scout keeps product controls in the signed-in dashboard and uses the Marquorum Support portal for verified human support. This guide shows where to start, what information is safe to provide, and which actions require private account verification.
Human support is asynchronous. Revenue Scout does not publish a phone line, staffed live chat, or response-time guarantee. If a self-service control is unavailable, email support@marquorum.com from the address connected to your account.
Sign in and choose the correct brand
Revenue Scout supports Google or a secure email sign-in link when those methods are available for the account. Use the same email address you used when creating or joining the account. Do not forward a secure sign-in link or team invitation.
If your account contains several brands, check the selected brand before changing campaign, opportunity, or billing settings. Brand-specific screens use the active workspace context. Team membership and billing can apply across the account, so read the scope shown beside a sensitive action.
If a sign-in link is expired or already used, request a new one. If you no longer control the account email, contact human support. Support may require additional verification and cannot bypass identity checks merely because someone knows a brand name or invoice detail.
Use Account settings for access and preferences
Open Account from the dashboard navigation. Account settings can show sign-in methods, active sessions, the current plan, notification preferences, team access, data export, and account closure controls. Some actions require a recent sign-in because they affect access, data, or other people.
Revenue Scout separates necessary service communication from optional progress or marketing preferences. Use the visible controls to change optional email preferences. A preference change should confirm the new state. Security, access, billing, and service messages may still be sent when they are needed to operate the account or complete a request.
If a preference control is temporarily unavailable, try again later or contact support. Do not treat the absence of a dashboard toggle as consent to send marketing messages.
Manage team access carefully
Account owners or authorized team administrators can invite people, choose an available role, change roles, cancel or resend pending invitations, remove members, and review who has access. A team invitation is intended for the named email address and can expire.
Every plan, including Free, includes team access. Team members are not sold as a separate higher-plan feature. The available roles still determine which brands and actions each person can access.
Current total user capacity is:
- Free: unlimited team members.
- Starter: unlimited team members.
- Growth: unlimited team members.
- Scale: unlimited team members.
- Pro: unlimited team members.
- Agency: unlimited team members.
Every plan includes all existing features and all seven platforms. The exact credit balance and monthly capacity appear in Plan and billing. Team access covers the account's brands according to the role shown in the product. Inviting a person does not create another Free credit grant.
Before removing someone or leaving a team, read the confirmation and the access consequences. A monthly plan change changes the credit allowance, not the available team feature. The product should show any access consequences before you confirm a sensitive action. Contact support if the visible team and billing state disagree.
Export your data
Use the data export control in Account settings when you need a copy of account information. The product prepares the export, updates its status, and provides a time-limited download when processing finishes. The current export is a JSON package divided into sections.
Keep the downloaded file private. It can contain brand, campaign, account, and activity information. If an export fails or expires, request a new export from the same control. Contact support if repeated attempts fail. Support should not email a private export to an unverified address.
Close access only after reviewing the effect
Account closure is a sensitive, destructive action. Open the closure review in Account settings, read when access will end, and check whether team access or paid service is affected. The product requires explicit confirmation and can require a recent sign-in.
Download any needed data first. Do not use account closure as a substitute for canceling one campaign, deleting one brand, leaving a team, or changing an optional email preference. Those actions have separate controls and different consequences.
If the closure state is unclear, stop and contact human support before confirming. Public knowledge cannot decide whether a specific subscription, refund, retention, or legal obligation continues after closure.
Open verified Revenue Scout Support
Open Help in the Revenue Scout dashboard. Copy the support reference when you need it. The page can open the central Marquorum Support portal with verified workspace context attached without placing personal information in the link.
If the verified handoff fails, use the email fallback shown on the page. Send the support reference, a concise description, the affected screen, and the approximate time. Never send a password, secure sign-in link, full payment-card number, session token, or private social-account credential.
You can also start at support.marquorum.com, choose Revenue Scout, and sign in through Revenue Scout if prompted. The verified product handoff carries only the safe workspace context needed by support. If support sends an email confirmation link, complete that confirmation before expecting private case access. Opening the email link alone does not create a signed-in support session. A public knowledge article or unverified email cannot expose a workspace or support record.
Understand case states and replies
The portal uses plain customer labels for the support lifecycle. Open means the case is active. With support means the support team needs to act. Needs your reply means support is waiting for information from you. Resolved means an answer or outcome has been provided. Closed means the conversation is finished.
Reply in the portal or by email when the case thread supports email replies. Keep the same thread so messages remain attached to the correct case. A new message about a different problem should become a new case rather than mixing unrelated account or billing decisions.
Add safe attachments
The portal accepts PDF, PNG, JPEG, TXT, and CSV files up to 5 MiB per upload. Files are stored privately and must pass a security scan before they can be downloaded. A pending scan is not a rejection. If an upload fails, the portal keeps the case or reply and gives you a separate attachment retry path.
Remove passwords, tokens, full payment details, unrelated personal information, and confidential third-party records before uploading. A screenshot should include only the part of the screen needed to understand the problem.
Know when a person must take over
Human review is required for private account inspection, access recovery, payment or invoice details, plan-state disputes, data and privacy requests, legal or security reports, and any action that changes a customer's account. Public knowledge can explain a process, but it cannot make or execute those decisions.
When the Revenue Scout Help assistant is active, it remains limited to the exact current approved public knowledge release. It must hand off rather than guess when the question depends on private data, uncertain facts, or a human decision. Human support remains available when the assistant is disabled, unavailable, or unable to answer safely.
Connect Revenue Scout to your team's tools
Open Connections in Revenue Scout to connect the tools your team uses for email, sales records, shared workspaces and notifications. The connector directory explains the twelve destinations and their workflows. Connections and Automations have different jobs: Connections establishes the account or destination; Automations defines which events and actions use it.
Choose the appropriate brand and destination before configuring a workflow. A connection can receive events only from its allowed brands. If your team role lets you view connections but not manage them, ask the account owner to add, verify or revoke the connection. Do not use another person's credentials to work around team access.
Choose the right connector
Gmail
Connection: Gmail.
Send the exact approved emails and scheduled follow-ups from a connected Gmail account. Address and thread checks run before due sends; replies and bounces stop remaining follow-ups. Social replies remain manually posted.
Setup: Save the connection name and brands, connect Gmail, then review the exact recipient, subject, message, timing and total provider cost before separately queueing the sequence. Connecting alone sends no email.
Workflow: Choose a lead with a supported email address, approve your message and follow-ups, then queue the sequence.
Connect your Gmail account to send the exact emails and follow-ups you approve. Review the sending mailbox, recipient, subject, body, timing and follow-ups before queueing the sequence. Revenue Scout checks the address and reads the thread before each due send. Replies and bounces stop remaining follow-ups. Connecting Gmail by itself does not queue a message, and reconnecting does not restart a stopped sequence.
Gmail outreach is separate from social replies. Revenue Scout prepares social replies for you to review, edit, copy and post manually. A saved social reply, lead discovery, CRM handoff or notification is not approval to send an email.
GoHighLevel
Connection: GoHighLevel.
Create or update contacts in a selected GoHighLevel location using reviewed mappings of available prospect evidence and the source conversation link.
Setup: Save the connection name and brands, connect GoHighLevel, choose an installed location when using a company sign-in, then review its existing contact fields. Setup does not write a contact.
Workflow: Connect a location, review its contact fields and route selected leads into that location.
Create or update contacts in the GoHighLevel location you choose. Complete sign-in, choose an installed location when using a company account, and review the existing contact fields. Map available conversation and prospect evidence to those fields before activating the handoff. Check the displayed location so one client's lead does not go to another client's account. Completing setup does not create a contact.
Salesforce
Connection: Salesforce.
Create or update Salesforce Leads or Contacts with reviewed mappings of available prospect evidence, including the original source URL.
Setup: Save the connection name and brands, connect Salesforce, choose Leads or Contacts and review the field mapping before any record is sent.
Workflow: Choose Leads or Contacts, confirm the field mapping and send selected prospect evidence to Salesforce.
Create or update Salesforce Leads or Contacts with the prospect evidence available in Revenue Scout. Choose the record type, review its fields and map the evidence to the correct destination fields. Check the source link and available contact or business details in the preview before activating the workflow. The mapping uses supported evidence; a missing value is not permission to invent a name, email address or company.
HubSpot
Connection: HubSpot.
Create or update HubSpot contacts using reviewed mappings of available prospect evidence and the original source URL.
Setup: Connect HubSpot, verify the intended account and review the available contact-property mapping before activating a handoff. Setup does not create a contact.
Workflow: Connect HubSpot, map contact properties and route selected prospect evidence into your existing account.
Map available prospect evidence to contact properties in your HubSpot account. Confirm the account and review each mapping before activating a workflow. Include the original conversation link where it helps your team understand why the prospect is relevant. A contact record is a handoff into your team's process, not proof that someone has become a customer.
Pipedrive
Connection: Pipedrive.
Create or update Pipedrive people using reviewed mappings of available prospect evidence and the original source link.
Setup: Save the connection name and brands, connect Pipedrive, verify the company and match existing person fields. Setup does not write a person.
Workflow: Verify your Pipedrive company, review the person-field mapping and hand off selected leads.
Create or update Pipedrive people with available prospect details and the original conversation context. Verify your Pipedrive company, choose existing person fields and review the mapping. Check that the destination company is the one used by the selected Revenue Scout brand. Completing setup does not write a person record.
Notion
Connection: Notion.
Create or update mapped Notion database pages with selected conversation evidence and sales information.
Setup: Save the connection name and brands, connect Notion, share an existing database, choose its data source and review the property mapping. Setup does not write a page.
Workflow: Share a database with the connection, review its property mapping and send selected conversation records.
Keep selected conversations and sales work in a mapped Notion database. Complete sign-in, share the existing database with the connection, and choose the database and data source presented during setup. Review the available properties and map the details your team needs before verifying the destination. Use the displayed database name to check that the handoff belongs in the intended workspace.
Airtable
Connection: Airtable.
Create or update mapped Airtable records with selected conversation evidence and sales stages.
Setup: Save the connection name and brands, connect Airtable, choose an authorized base and table and review the field mapping before it receives records.
Workflow: Choose a base and table, review the field mapping and keep selected lead records in Airtable.
Keep selected conversations and sales stages in a mapped Airtable table. Choose an authorized base and table, then review the table's fields. Map the supported lead evidence to the intended fields and confirm the destination before it can receive records. A similarly named table in another base is a different destination, so check both names.
Google Sheets
Connection: Google Sheets.
Create or update rows in a chosen Google spreadsheet and tab using reviewed mappings of conversation details, sales stages and source links.
Setup: Save the connection name and brands, connect Google, choose a spreadsheet and tab and review its column mapping, including record and delivery identifiers, before it receives records.
Workflow: Select a spreadsheet and tab, confirm the column mapping and send the records your team needs.
Send selected conversations and sales stages to the spreadsheet and tab your team uses. Complete Google sign-in, select the spreadsheet, choose its tab and header row, then review the column mapping. Map the required record key and operation ID once each, alongside the fields you need, so the connection can recognize its records and operations. Verify the selected target after reviewing the headers.
Slack
Connection: Slack.
Send selected conversation notifications to a configured Slack incoming webhook.
Setup: Create an incoming webhook for the chosen Slack channel, save its destination with the connection name and brands, then review the notification and rule before activation.
Workflow: Choose a channel and send a notification when an event matches your approved workflow.
Bring selected conversations into a chosen Slack channel. Configure the channel's destination, preview the verification message and confirm the destination before using it in a rule. Choose which events should notify the team in Automations. The notification gives your colleagues context to discuss and act on; it does not post a social reply on their behalf.
Discord
Connection: Discord.
Send selected conversation notifications to a configured Discord incoming webhook.
Setup: Create an incoming webhook for the chosen Discord channel, save its destination with the connection name and brands, then review the notification and rule before activation.
Workflow: Connect the channel’s incoming webhook and route selected conversation alerts to your team.
Send selected conversations through a Discord incoming webhook for the channel your team uses. Configure the webhook destination in Connections, preview its verification message and confirm the target. Then choose the events and notification action in Automations. Keep the webhook URL private, since it contains the destination's access information.
Teams Workflows
Connection: Teams Workflows.
Send selected conversation events to a customer-configured Microsoft Teams Workflow webhook. Workflow acceptance is distinct from confirmed channel delivery.
Setup: Configure the Teams workflow and its webhook destination, save that destination with the connection name and brands, then review the event and rule before activation.
Workflow: Configure your Teams workflow, connect its webhook and approve the events sent to it.
Pass selected conversations to a workflow your team has configured in Teams. Configure that workflow's webhook destination, preview the endpoint test and verify it in Connections. The displayed status, Endpoint test accepted, confirms workflow acceptance. Check Teams separately to confirm that the configured workflow put the message in the intended channel. An accepted endpoint test is not confirmation of channel delivery.
Signed webhook, Make and n8n
Connection: Signed webhook.
Send selected events to a signature-verifying receiver in Make, n8n or a custom system. Receiver acceptance does not establish completion of downstream actions.
Setup: Configure a receiver to verify the signature and timestamp and retain delivery identifiers. Save its URL and signing secret with the connection name and brands, then review the destination and rule before activation.
Workflow: Configure a receiver to verify signatures and record delivery IDs, then connect and approve its event workflow.
Send selected events to a receiver your team controls. Configure the receiver to verify the request signature and record delivery identifiers so it can recognize repeated requests before acting. Make and n8n use this Signed webhook route, rather than separate native connectors. Connections includes receiver setup guidance and an n8n inbox example.
Keep the signing secret and destination access details in the intended private configuration. Do not paste them into a support case, shared document, screenshot or chat. Choose the events and destination in Revenue Scout, preview the content, and configure the receiver's downstream actions for your own process.
Set up and verify the destination
- Open Connections, choose the tool and give the connection a useful name.
- Select the allowed brands. Confirm that your account and brand access cover the intended work.
- Connect the provider account or configure the destination requested by that connector. Complete the provider's sign-in and authorization flow in its own interface.
- For CRMs and workspaces, choose the actual account, location, record type, database, table or spreadsheet tab. Review the existing fields and map the available evidence.
- Complete the connector's verification step. For a destination test, read the preview and confirm the exact target before requesting verification. The test can send a verification message to that destination, so use a channel or receiver you are authorized to test.
- Check the refreshed connection status and the verified destination details. Saving a connection or returning from provider sign-in is not the same as verifying a complete target.
The dashboard connector workflow does not require a Revenue Scout API key. Use only the service authorization or configuration requested by the chosen connector. Customer API and MCP access are separate settings and do not replace connection setup.
Preview an automation before activating it
Open Automations after the connection is verified. Choose the brand, triggering events, conditions, destination and supported action for the workflow. A CRM action creates or updates its supported record; a workspace action sends selected records to the mapped destination; a notification action informs the chosen team channel or receiver.
Preview the matching records, actual mapped values, message content and destination before activating the rule. Check that the selected brand and provider account match. Available evidence can include a source link, excerpt, name, business detail, stage or follow-up information, depending on the destination. Use the preview to check what will actually be sent rather than assuming every lead has every possible field.
For Gmail, review and approve the exact recipient, subject, body, timing and follow-ups before queueing the sequence. Current address and thread checks remain part of due sends. Keep that deliberate email action distinct from activating a CRM handoff or team notification.
Connection setup does not replace the recipient's communication preferences or establish permission to contact a person. Choose appropriate recipients and messages, and respect recorded opt-outs. Customers remain responsible for their own outreach and social posting.
Pause a workflow or disconnect a tool
Manage rules in Automations and connected accounts in Connections. Pause the relevant rule when you want it to stop starting new work. Revoke or disconnect the connection when the account or destination should no longer receive new authorized work. Review the consequences shown for that connector before confirming, including any provider disconnection step.
Pausing or disconnecting does not recall a message or record already accepted by another service. Check the workflow's recorded outcome and the destination if a delivery was already in progress. Reconnecting Gmail does not restart stopped email sequences; review their recorded state before deciding on a new action.
Recover a connection that needs attention
Start with the connection's displayed message and current status. If provider sign-in was not completed, continue from the saved connection and connect the same intended account again. If authorization was revoked or has expired, reconnect through the provider's normal flow and check the verified account afterward.
If an account, location, database, table, property or spreadsheet header changed, review the saved target and mapping. Choose the current intended destination and complete its verification again before resuming the affected rule. Confirm allowed brands and team access as well as provider access. A provider authorization cannot grant access to a Revenue Scout brand your team role does not allow.
Read the workflow's delivery result and check the destination before retrying an uncertain action. An endpoint accepting a request is not the same as a person reading an email, a CRM record being qualified, or a Teams message reaching its channel. Do not repeatedly create another contact, row, notification or email sequence merely because confirmation is unclear.
If the displayed recovery step does not resolve the problem, use Help to open verified support. Include the connector name, connection label, affected brand, screen, approximate time, displayed error and any safe operation reference. Remove credentials, signing secrets, webhook URLs with access information, private mailbox content and unrelated prospect data. Support can investigate the verified account and recorded outcome without asking you to expose a secret.