Skip to main content
Switching from RevenueHero to Default means rebuilding your RevenueHero routers as Default workflows, your teams and distribution rules as queues and routing policies, and your meeting types as Default events. Default connects to Salesforce or HubSpot, picks up the forms already on your website, and enriches, matches, routes, and books each lead in 1 workflow. This guide is for admins. Default does not import RevenueHero routers, rules, or meeting types, so plan to rebuild them and move your forms over 1 at a time.

RevenueHero and Default at a glance

RevenueHero Inbound Routers in Default

A RevenueHero Inbound Router maps a form, disqualifies some prospects, checks matching rules, then applies distribution rules. A Default workflow runs the same steps as nodes, in the order you place them.

RevenueHero round robin in Default

Enrich and qualify leads in Default

RevenueHero pulls firmographic data from a connected provider when a visitor submits. In Default, an Enrich Data node right after the Form Submission trigger runs before any routing node.
  • Providers: waterfalls use Clearbit, Apollo, People Data Labs, and Wiza. Default manages access to these providers, so you don’t need an account or API key with any of them.
  • Email checks: a waterfall can also validate emails with Abstract Email Reputation or Icypeas.
  • Qualify and route: a Multi-Branch node or a Rules of Engagement ruleset can use the enriched values, for example company size or country.
  • CRM hygiene: Create Record or Update Record can write the enriched values to Salesforce or HubSpot.
See Enrichment nodes.

Rebuild a RevenueHero Inbound Router as a Default workflow

This example rebuilds an Inbound Router for a Request a demo form. Known accounts book with the account owner, new companies with more than 500 employees book the Enterprise demo event, and everyone else books the Demo event. Both events are Team events hosted by queues.
1

Start from the form

In Workflows, create a workflow and add the Form Submission trigger. Set Connected Form to Request a demo.
2

Enrich the lead

Add Enrich Data with Enrichment target set to Both and your waterfall as Enrichment source.
3

Disqualify the prospects you do not book

Add Multi-Branch with a branch for the prospects you disqualify, for example a country you do not sell to. On that branch, add Redirect to a page on your site. Continue from Else.
4

Match the account

Add Match Record with Record set to Account. Compare Website with the submitted email using domain matches and Domain from email.
5

Book known accounts with their owner

On Match, add Display Scheduler with the Demo event. Turn off Use event hosts and set the host to the matched Account’s owner.
6

Distribute new companies

On No Match, add Multi-Branch with an Enterprise branch for more than 500 employees. Add Display Scheduler with the Enterprise demo event on Enterprise, and with the Demo event on Else. Keep Use event hosts on, so each event’s queue picks the rep.
7

Follow up on prospects who do not book

On each Not booked branch, add Send Slack Message, or Round-Robin and Update Record to give the lead an owner for follow-up.
8

Test and publish

Select Test, then Run Test once for each case: a known account, a large new company, a small new company, and a disqualified prospect. Then select Publish, and turn on the deployment switch so the status reads Live.
A workflow test performs real actions. It can book meetings, count routing assignments, and write to your CRM. Use test people.

Move from RevenueHero to Default step by step

1

Connect your CRM and conferencing tool

Select Settings in the sidebar, then Integrations under Workspace Settings. Connect Salesforce or HubSpot. Salesforce needs the Default managed package installed first. See Salesforce and HubSpot. If your team meets on Zoom, connect Zoom once for the workspace. Google Meet and Microsoft Teams links come from each member’s own calendar connection.
2

Invite your team and connect calendars

In Settings → Users, select Invite People. Each member connects Google Calendar or Outlook Calendar and sets working hours. See Member onboarding.
3

Map each rep to their CRM user

In Settings → Users, add each rep’s Salesforce User ID or HubSpot Owner ID. Default needs this mapping to write CRM owners and to use a record owner as a meeting host. See Users.
4

Rebuild Teams and Distribution Rules as queues

In Routing → Policies, select Create Policy, and choose the distribution rule and Slots Rule. In Routing → Queues, select Create Queue for each team. See Policies and Queues.
5

Rebuild Meeting Types as events

In Scheduling → Event Types, select Create new event. Use a Team event with a queue as host for each distribution rule, and a Quick event for personal links. Assign reminder and notification templates under Messages. See Events.
6

Install the Pixel and add your forms

Open Signals, select Add Domain, and install the Pixel snippet. Then open the domain’s menu, select Catalog forms, add each form you mapped in RevenueHero, and map its fields. See Set up the Pixel and Forms SDK.
7

Rebuild routers and Relays

Build 1 workflow for each Inbound Router, as in Rebuild a RevenueHero Inbound Router. For Relays, build a workflow with the Extension trigger. For Campaign Routers, share booking links from the matching Team event.
8

Log meetings in your CRM

Build a workflow with the Meeting Status trigger set to Booked. Find the guest’s record with Match Record, then add Create Activity for Salesforce or Create Engagement for HubSpot.
9

Switch over 1 form at a time

When a workflow passes its tests, publish it and set it live. Then remove the RevenueHero script from that form’s pages, so visitors see 1 scheduler.

What does not carry over from RevenueHero

  • Configuration. Default has no importer for RevenueHero routers, rules, teams, or meeting types. You rebuild them in Default.
  • Meeting history and reports. Meetings, routing logs, and reports stay in RevenueHero. Default starts its own meeting and assignment records from the first workflow run.
  • Other CRMs. Default connects to Salesforce and HubSpot. Zoho CRM and Freshsales are not supported. Attio is coming soon.
  • RevenueHero forms. Default doesn’t design or host forms, so there is no hosted form page behind a link. Put the form on your website, either one you add with Catalog forms or one you create in Default with Create new → New form. See Create a form in Default. For handoffs, the Chrome extension needs only the lead’s email to route.
  • Owner lookup from a link. A Default booking link books with the link’s hosts. It does not look up a CRM owner from URL parameters, the way a prefilled Campaign Router link can.
  • Meeting and prospect limits. Default has no cap on how many meetings a rep takes, or on how often a prospect or company can book.
  • Nominees. Default has no named backup for each rep. Display Scheduler has 1 Fallback Host (Optional) for the node.
  • Other enrichment providers. Crustdata, Ocean.io, ZoomInfo, and ZeroBounce are not Default providers. Default’s waterfalls use Clearbit, Apollo, People Data Labs, and Wiza.
  • Other entry points. RevenueHero’s Intercom widget, Gong, and Appcues integrations have no Default equivalent.
  • Other languages. The Default scheduler is in English.
  • Other conferencing tools. Default adds Zoom, Google Meet, or Microsoft Teams links, or an in-person location. Daily and custom conference links are not supported.
Related: Default vs RevenueHero