Overview
The Steep integration brings seminar, workshop and webinar registrations from Steep into Swivel automatically. Swivel checks Steep for new registrations every 15 minutes.
Each Steep registration becomes three things in Swivel:
A contact. Matched on Steep's person ID, so a returning registrant is updated, not duplicated.
A marketing event. One per Steep event. Every registration for the same Steep event lands on the same Swivel event.
A row on the event's roster. Registered, Confirmed, Status and Outcome are set from the registration's status in Steep.
You decide where every piece of Steep data goes in your Swivel fields and lists. The connection is read-only: Swivel never writes anything back to Steep.
Who can set it up: Account owners and managers. Staff users work with the contacts, events and rosters the sync creates.
📌 Note: Steep must be turned on for your firm before you can connect it. If you're an owner or manager and don't see Integrations under Settings → Account Settings, contact your Swivel representative.
Before You Start
Have these ready:
An owner or manager role in Swivel. Only owners and managers can open the Steep settings, connect or disconnect Steep, change mappings and export sync history.
Your Steep API key. In Steep, go to Account settings → API keys and copy your firm's key. Only a Steep owner can see it. If that section is missing, ask whoever set up your Steep account.
About 20–30 minutes. Changes save as you go, so you can stop and pick up later.
Your seminar lists. Know which lead sources, marketing event types and campaign types you use for seminars, and which agent should own events when the presenter isn't a Swivel user.
What the Integration Does and Doesn't Do
The Integration Does | The Integration Doesn't |
Check Steep for new registrations every 15 minutes and refresh rosters for recent and upcoming events. | Write anything back to Steep. |
Fill empty fields and add a new email or phone as an extra record. | Overwrite data or attendance your staff entered. |
Import past events up to 90 days back, if you choose. | Run automations for imported past events. |
Run your new-lead automations, exactly as for a lead entered by hand. | Grant texting consent, whatever Steep sends. |
Match contacts on Steep's person ID. | Match contacts on name, email or phone. |
Set Up the Steep Integration
Step 1: Open Steep in Integrations
Select Settings.
Under Account Settings, select Integrations.
On the Steep card, click Connect Account. If setup was started before, the card shows Setup unfinished and the button reads Finish setup.
Step 2: Connect Your Steep API Key
Paste your Steep API key into the key field. Click Show to check it.
Click Check key. Swivel shows Checking with Steep… while it confirms the key.
When Steep accepts the key, a green Key accepted badge appears with your Steep account name and a shortened account number.
If Steep has had no registrations in the last 90 days, your account name appears after the first registration arrives.
Sample registrations: After the key is accepted, Swivel fetches up to 25 recent Steep registrations from the last 30 days (or 90 days if there are fewer). They show example values on the mapping pages and previews. Samples are stored encrypted and deleted when syncing starts, or after 14 days if setup isn't finished. Nothing is written to your contacts or events during setup.
🔍 Tip: Your key is encrypted and never shown in full again. The key field always starts blank, so paste the key again whenever you're asked for it.
⚠️ Important: If Swivel says Steep rejected this key, the key was mistyped, has expired or belongs to a different Steep account. Copy it from Steep again, in full, and click Check key.
If Steep Doesn't Answer
If Steep is slow or briefly unavailable, Swivel says Steep didn't answer (for example, "Steep took too long to answer"). This isn't a rejection. Your key stays saved and nothing changes. Click Check again to retry without retyping the key.
If a check runs for about three minutes, Swivel shows This is taking longer than it should with a Check again option.
Step 3: Set the Time Zone and Choose Whether to Import Past Events
Set Steep's Time Zone
Steep sends event times without a time zone, so Swivel reads them in the zone you choose.
Choose a time zone from the dropdown.
Check the time of your newest sample registration, shown under the dropdown. If it looks a few hours off, choose a different zone.
Click Save time zone. Changes apply to the next sync.
⚠️ Important: If your newest registration would be in the future in the zone you picked, Swivel shows a warning. A wrong time zone can cause registrations to be missed.
Choose Whether to Import Past Events
By default, Swivel syncs current and upcoming events only. Past registrations stay in Steep.
To import recent history, choose Last 7 days, Last 30 days or Last 90 days and click Save.
If you leave it at None, you can import past events later from the Steep page.
🚧 Important: Past events import in the background without running your automations, so past attendees won't receive welcome emails, texts or tasks. After syncing starts, you can extend the range (for example, from 7 to 30 days) but you can't shorten it.
Step 4: Review AI-Suggested Fields (Optional)
Steep, and the Catchlight profile data that comes with it, may send details your firm has no field for, such as a Facebook profile link or an estimated income band. If AI suggestions are turned on for your firm, Swivel proposes new custom fields only for data that has no home in Swivel.
AI suggestions are available during setup only. After syncing starts, you map new data yourself.
How AI Suggestions Work
They start automatically when Steep accepts your key. The mapping pages show Looking for suggestions…, then a Run again button when done. If no look has run yet, the button reads Get AI suggestions. If a look is stuck for more than 20 minutes, the button reads Restart.
Confident matches are filled in as suggestions on open rows (rows marked To decide, or holding only a suggestion with no destination) on unfinished steps. Less certain matches appear at the top of the row's picker under Most likely. Rows you've edited or left out are never changed.
To see results, wait for the Suggested new fields step to update on its own. On other mapping steps, reload the page. You can keep mapping in the meantime.
If it can't finish, the step says Couldn't look for suggestions or Stopped early. Click Run again. Running again never brings back suggestions you already created or skipped.
📌 Note: AI only sees names and labels, such as Steep's field names and list values, and the names of your custom fields, lead sources, marketing event types and tags. It never sees registrant details such as names, emails, phone numbers or sample values. AI suggestions are included at no extra cost.
Review Each Suggested Field
When there are fields to propose, a Suggested new fields step appears first. Each card names the Steep data, the proposed field and its settings.
Edit the Name, Type (Text, Number, Currency or Choice) and Visibility(Visible to everyone, or Masked: click to reveal) if needed.
Click Create field to add the field under Contact custom fields and map the Steep data to it. Or click Skip if you don't want a new field.
Skipping only dismisses the card. The row stays To decide on its step, and on a required step it still needs a decision before syncing can start.
Ranges such as income or home value are proposed as Choice fields with one option per band. Estimates about a person are proposed as masked fields.
Skip for now in the bottom bar moves on to Defaults and leaves the cards for later.
Skipped cards are kept in a collapsed Skipped list. Click Bring back to restore one.
When every card is handled, the step reads All set.
If you create a field after syncing starts, and it would show an estimate about a person to everyone, Swivel asks you to acknowledge it first.
Undo a Created or Skipped Field
After you create or skip a field, a confirmation with Undo appears at the top of the step.
Undoing a skip puts the card back.
Undoing a created field during setup deletes the field, restores the row and puts the card back.
Undo isn't available (Swivel shows Can't undo and the reason) once the field has a value, the row is mapped elsewhere, another row uses the field, the field was deleted, or syncing has started.
🔍 Tip: Rename suggested fields to match how your team talks.
Step 5: Map Your Steep Data
Mapping decides where each piece of Steep data lands in Swivel. It has five groups: Defaults, Contact fields, Event fields, Registration and Enrichment. Swivel pre-fills a suggestion wherever it can, so for most rows you only need to check it.
There's no Save button. Every change saves as you go and applies to the next sync.
Row Statuses
Status | Meaning |
To decide | Needs a decision from you. |
Mapped | The data goes to at least one place in Swivel. |
Check this | The row has a warning, such as sensitive data going somewhere unmasked. |
Left out | You chose not to import it. |
Set by Steep | Handled automatically, such as Steep's own IDs. |
Never imported | Data Swivel never takes from Steep, such as texting consent. |
Rows marked Suggested hold Swivel's suggestion. If you change one, it shows Edited with an Undo link.
Tools on the Mapping Pages
Filter chips: To decide is the fastest way to finish a group. Check these shows rows with warnings. Sensitive (Enrichment only) shows inferred personal data.
Search this group filters as you type. Jump to moves to a section.
Accept suggestions accepts every suggestion in the group. Restore suggestions resets every row to Swivel's suggestion.
The bottom bar shows running counts and the Preview contact and Preview roster buttons.
Choose Where Data Goes
Click Choose a destination on a row.
Type to search, or pick from Most likely. A field another row already fills is labeled.
To send the data to more places (up to four), click + Add destinationunder the mapped row.
To leave a row out, choose Never import this, or hover over the row and click the ⃠ button. Click ⃠ again to restore the row.
Map List Values
Some Steep fields are lists, such as lead source or event type. Each value gets its own row, plus an Any other value row that catches new values Steep sends later. Yes/no flags have no Any other value row.
Map several values at once: Tick the boxes beside them (Shift-click selects a run), then use Send values to…, Set the value… or Never import these. Registration status values are mapped one at a time.
Create a missing value: If a Steep value doesn't exist in Swivel, the picker offers to create it, for example Create 'Facebook' as a new lead source. The option is added the first time a registration needs it.
Defaults
Defaults tell Swivel what to use for everything it creates, since Steep doesn't send this information.
Default | What It Controls | Good Starting Point |
Contact type for new leads | The type new registrants are created as. Also decides which custom fields they can have. | Individual |
Contact category for new leads | Your Lead / Client / Beneficiary grouping. | Lead |
Contact status for new leads | Where a new registrant enters your pipeline. | New |
Marketing event type for new events | Used unless the event type mapping says otherwise. | Your seminar or workshop type |
Campaign for new events | One campaign for all events, or A new campaign per event (named after and dated to the event, under the campaign type you choose). Re-syncs reuse the campaign already created. | A new campaign per event, if you track ROI per seminar |
Assigned agent when the presenter does not match | The agent who owns events whose Steep presenter matches no Swivel agent. | Your lead advisor, or Unspecified |
⚠️ Important: New leads created by the sync trigger your automations exactly as a lead entered by hand would. Check your new-lead workflows before you start syncing.
Contact Fields
Name, email, phone and address go to the contact. Email, phone and address create separate records in Swivel. An email becomes primary when the contact has none.
Steep's person ID is always stored as the contact's source key. This is how returning registrants are recognized.
The picker shows account-wide custom fields plus those of the contact type set in Defaults. If the sync later matches a contact of a different type without that field, nothing is stored and it's listed under Waiting for a decision.
⚠️ Important: The sync never sets texting consent, and Steep's texting opt-in can't be mapped. Consent lives on the phone record in Swivel, and your staff record it when the contact gives it.
Event Fields
Event name, start and end time, presenter and venue go to the marketing event. Times are read in the Steep time zone from Step 3.
The presenter is matched to an agent by exact full name (capitalization doesn't matter). If nobody matches, the default agent is used.
Map each Steep event type to one of your marketing event types, including Any other value as a fallback.
Registration
Steep stores a registration's progress as one status. Swivel's roster splits it into four places: the Registered and Confirmed checkboxes, Status and Outcome. One Steep status can set several of them. For example, Appointment Set can set Status to Attended and Outcome to Appointment set.
Leave Tick Registered for every status on so people marked Attended also show as registered.
Click Preview roster to see how each Steep status will look on a roster.
Party size, guest names and meal choices are stored with the registration, so each event keeps its own values. Steep's registration ID and time are always stored with the roster row.
🔍 Tip: Watched Replay is a judgment call. Some firms count it as Attended; others keep it as Pending with Outcome set to Follow up.
Enrichment (optional)
Steep includes Catchlight profile data such as income and asset bands, age range, life events, interests and work details. You can map what's useful, leave rows undecided (they import nothing) or, during setup, click Finish without enrichment to set every enrichment row to Never import.
Minimum match confidence: Catchlight rates how sure it is that it found the right person. The recommended setting, Good or better, drops enrichment from weaker matches.
Prohibited records: When Catchlight marks a person as prohibited from enrichment, none of their profile data is stored. The contact and registration still sync.
Ranges: Income, investable assets and home value arrive as a minimum and maximum. Choose One range for one choice field with an option per band (easy to filter), or Two fields to keep exact numbers. Projected revenue can only be stored as two fields.
Life events and interests are suggested as tags, such as "Life event - 1-2 Year from Retirement". Where a life event matches one of your products, Swivel also offers a one-click product interest.
For how sensitive data is handled, see Sensitive data and masking below.
Preview a Contact
Click Preview contact to see what a sample registrant would get with your current mappings: fields, tags, product interests and roster row. Nothing is written to Swivel.
After syncing starts, Preview contact fetches up to 25 recent registrations from Steep again. They're stored encrypted for about a day, and sample values show on the mapping rows while they're kept.
Step 6: Preview the First Sync and Start Syncing
The setup page's main button reads Start syncing… once Defaults, Contact fields, Event fields and Registration have nothing left to decide and no suggested fields are waiting. Enrichment doesn't need to be finished. Until then, the button takes you to the next unfinished step.
Syncing can't start while a required row is undecided, a required default is missing, a mapping needs a new choice, or sensitive data is mapped somewhere unmasked without acknowledgement. Swivel lists what's left (for example, 3 things to decide before syncing starts), each with a Take me there link.
Optional: Click Preview first sync, then Run a test. Swivel rehearses the first sync against current and upcoming events and reports the contacts and events it would create or match, roster statuses, tags, new list options and any sensitive data stored unmasked. Nothing is written. After changing a mapping, click Run it again. A test can take a few minutes.
Click Start syncing… to open a summary of what the first sync will do.
Review the summary, then click Start syncing.
The first sync starts right away, and setup samples are deleted. First registrations arrive within 15 minutes.
⚠️ Important: If sensitive data (such as age or income) is mapped somewhere that can't be masked, like a tag or a plain field, the summary lists it. You must tick a box to acknowledge it before Start syncing is enabled. Your name and the time are recorded.
📌 Note: The first sync reads the last month of registrations, so it can take 15 minutes or more for a busy firm. It runs in the background, and you don't need to stay on the page. Later syncs take a few seconds.
How Each Sync Works
Frequency: Every 15 minutes, Swivel asks Steep for new registrations.
Contacts: Matched on Steep's person ID. Returning registrants are updated. New registrants are created with your Defaults.
Events: Matched on Steep's event ID, so all registrations for one seminar land on the same marketing event.
Roster refreshes: Status changes such as Attended or No show arrive through separate roster refreshes:
Events starting in the next 7 days, or that started in the last 2 days: every hour.
Other events: once a day, until 14 days after the event started.
After 14 days: no longer refreshed.
Staff changes are kept: Swivel fills empty fields only. For a returning contact, a new email or phone is added as an extra record, tags and product interests are added, custom fields are filled only if empty, and an address is added only if the contact has none. On rosters, Swivel changes only values it set itself.
Outages: If Steep is briefly unreachable, the next sync picks up where the last one stopped.
Failed registrations: If one registration can't be saved (for example, no last name), it's listed under Waiting for a decision and the rest sync normally.
Deleted records: If you delete a contact, marketing event or roster row the sync created, Swivel won't recreate it. Registrations that need it are skipped and noted in the exported sync history.
Monitor Syncs on the Sync Activity Page
When syncing, the Steep card on the Integrations page shows Syncing, the last sync time and anything waiting for you (for example, "2 values and 1 new field waiting to be mapped"). The number beside Integrations in the sidebar counts the same items.
To open Sync activity, click Manage on the Steep card, or View sync activity on the Steep page.
What's on the Sync Activity Page
Sync timeline: One mark per sync in the last 24 hours, colored for registrations brought in, nothing new, partial, or past events imported.
Brought in since you connected: Totals for registrations, new contacts, marketing events and roster rows.
Events from Steep: Each event with its date, roster size and last change. Click an event to open it. Purple bars mark imported past events.
Sync log: The last 7 days, newest first, in your Steep time zone. Quiet syncs are grouped; click the arrow to expand. Click Show earlier days to go back further. History is kept for 13 months.
Waiting for a decision: Anything Swivel needs you to decide.
The page updates while it's open. Running syncs appear in the log right away (for example, "Sync now by Quinn: running…"). When new results arrive, click Refresh on the New sync results are ready notice.
Partial and failed syncs are marked in amber and explain what happened, for example "Brought in 1, and 3 registrations couldn't be saved" or "Steep could not be reached. Retried at 8:57 am but it happened again".
Sync Now
To sync without waiting, click Sync now at the top of the page. Swivel checks Steep for new registrations and today's rosters.
The button shows Syncing…, then Synced just now.
If Steep didn't answer, it shows Didn't go through.
You can sync again a couple of minutes after the last sync started.
Export Sync History
Click Export history above the Sync log.
Choose Last 30 days, Last 90 days or dates up to 13 months back.
Click Start export.
The spreadsheet lists every registration Steep sent and what Swivel did with it: time, Steep event and date, action taken, contact link, sync type, contact name and email, any failure reason and the Steep registration ID.
📌 Note: Exports contain client names and emails, so only owners and managers can run them, and each export is recorded.
Connection Problems
Connection problems appear at the top of the Steep page and the Sync activity page. The Integrations card shows Key rejected, Not syncing: Steep isn't answering or Syncing is overdue.
Message | What It Means | What to Do |
Steep hasn't answered in a while | Three syncs in a row failed. Swivel shows how long and why. | Nothing. Syncing resumes on its own and picks up where it stopped. Owners and the manager who started syncing are emailed when it starts and when it recovers. |
Steep rejected this key, so syncing has stopped | The key was revoked or rotated. New registrations wait in Steep. | Click Replace key and paste a new key. Owners and the manager who started syncing are emailed. |
Syncing is overdue | No sync has started for more than 30 minutes. New registrations wait in Steep. | If it continues, contact Swivel support. |
Resolve Items Waiting for a Decision
Steep can start sending a new value (such as a new lead source) or a new field at any time. Swivel lists these under Waiting for a decision on Sync activity and counts them on the sidebar badge.
Every day at 8 am in your Steep time zone, owners and the manager who started syncing receive an email listing new items, including registrations that still failed after three tries.
What Happens Before You Decide
New value: Uses the field's Any other value mapping, so nothing is lost. If Any other value is set to never import, nothing is stored until you map the new value.
New field: Not stored until you map it.
Map or Dismiss an Item
Click Review to expand a group.
Click Map to open the mapping group at the new row. The new row starts out the same as the field's Any other value row, so check it and change it if needed.
For a new field you don't want, click Ignore to mark it as never imported. To see the whole group, click Open in mappings.
Technical details such as internal IDs, timestamps and map coordinates are left out of the list automatically. Resolved entries are removed after 90 days.
Types of Items
Item | Meaning | What to Do |
New values (for example, "3 Lead source values") | Values Steep started sending. Shows how many registrations carried them and whether they're kept in the meantime. | Click Review, then Map. |
A registration Swivel couldn't save | Something in Steep's data blocked it, such as no last name. Shows the last characters of Steep's reference. | Correct it in Steep. Swivel picks up the fix while it's still refreshing that event's roster. Click Dismiss to clear it. |
A registration that failed to save | Swivel is still retrying. Shows the reason and number of failures. | Nothing, unless it keeps failing. |
A past event Swivel couldn't import | The event's roster kept timing out during a past-events import. | The import continues without it. |
Not available for every contact or event this field reaches | The custom field you mapped doesn't exist on some matched contacts' or events' types. Nothing is stored for those. | Click Dismiss, or map to an account-wide field. |
Import Past Events
If you chose to import past events, the import starts when syncing begins. Swivel finds events a week at a time, then imports each event's roster with your mappings. Progress shows on the Steep page and Sync activity, for example "Importing past events since Sep 1: 12 of 40 events".
Automations never run for past events, including later status changes on them.
Past events appear in purple under Events from Steep and as Past events imported in the Sync log.
If every event in the range is already in Swivel, the banner says there's nothing new to import.
Extend the Import Range
After an import finishes, choose a longer range on the Steep page and click Import. Only the extra days are imported, and events already in Swivel are skipped. The range counts back from the day syncing started, not from today. If you chose None during setup, start an import the same way.
If the Import is Interrupted
Steep stops answering: The banner shows Steep isn't answering right now. Retrying shortly, and Swivel retries on its own. Everything imported so far is kept.
One event keeps timing out: Swivel skips it, finishes the rest and lists it under Waiting for a decision.
The import stops after three outages in a row, a rejected key or a connection change. The banner reads, for example, The import of past events stopped after 12 of 40 events. Click Resume import on the Steep page or Sync activity. It continues where it stopped without re-importing anything.
Some registrations couldn't be saved: The banner says how many, and they're listed on Sync activity.
Sensitive Data and Masking
Catchlight's income, investable assets, home value, projected revenue, age and wealth segment are estimates about a named person, not facts the client provided. Swivel marks these rows as sensitive and suggests storing them in a masked custom field.
Masked fields show Click to reveal on the contact. Every reveal is logged with who looked and when.
Tags, product interests and ordinary fields can't be masked. Anyone who can open the contact can see them. Rows that send sensitive data somewhere unmasked are marked Check this and need your acknowledgement before syncing starts.
After syncing starts, mapping a sensitive row somewhere unmasked isn't saved until you click Acknowledge and save. Each change needs its own acknowledgement, so the bulk bar can't do this. Map those rows one at a time.
Wealth segment and investable assets describe the same estimate, as named bands (Mass Market through Ultra High Net Worth) or as amounts. Map one. If you map both, Swivel warns that the estimate would be stored twice. If you map neither, it isn't imported.
📌 Note: Masked custom fields that belong to a contact type can't be used as list columns or filters. Masked account-wide fields, which Create field makes, can be list columns, but filtering is limited to "Any of". If your team needs to filter on a band, weigh that against keeping it masked.
Find Steep Events in Swivel
Each Steep event appears under Marketing → Events with its start time, venue, event type, assigned agent, campaign and Steep's event ID as the source key.
The event's roster lists every registrant with Registered, Confirmed, Status and Outcome set from Steep. Staff can keep working the roster as usual; the sync won't undo their changes.
Change Settings After Setup
Edit Mappings
On the Steep page, click Edit mappings. Changes save as you go and apply to the next sync. They don't change contacts or events already brought in. On the last step, click Done to return to Sync activity.
AI suggestions aren't available after setup. Map new values and fields from Waiting for a decision.
Replace the API Key
On the Steep page, click Replace key.
Paste the new key under Replace the Steep API key.
Click the Replace key button below it.
Syncing continues with the new key while Swivel checks it. Until Steep confirms it, the badge reads Key not verified yet.
If Steep doesn't answer, click Check again or replace the key again.
If Steep rejects the new key, syncing stops until you replace it again.
If the new key belongs to a different Steep account, registrations from the old account stay in Swivel and syncing from the new account starts from today.
Change the Time Zone or Past-Events Range
You can change the time zone at any time; it applies to the next sync. You can extend the past-events range after any running import finishes.
Disconnect Steep
Open Sync activity and click Disconnect Steep under Waiting for a decision. During setup, click Disconnect on the Steep page.
Confirm.
Imported data stays in Swivel and your mappings are kept. Disconnecting deletes the saved key and sample registrations and stops any past-events import.
To reconnect, paste a key again. You return to setup with your mappings as you left them. Syncing resumes after you click Start syncing.
🔍 Tip: On a phone or small tablet, the mapping pages are read-only. You can review mappings and use the previews, but make changes from a computer.
Keyboard Shortcuts on the Mapping Pages
Key | Action |
j / k | Move to the next or previous row |
Enter | Open the picker for the current row |
x or Space | Select a value row (Shift-click selects a run) |
/ | Jump to the search box |
Esc | Close the picker or clear the selection |
Messages You Might See
Connecting and Checking the Key
Message | What It Means and What to Do |
Steep is still checking the key | You tried to replace the key while a check was running. Wait a moment and try again. |
This is taking longer than it should | A key check has run for about three minutes. Click Check again. |
Steep rejected this key | Copy the key from Steep again, in full, and retry. |
No registrations in the last 90 days yet | The key works. Your account name appears after the first registration arrives. |
Steep took too long to answer during the test | Shown by Preview first sync when Steep is slow. Nothing changed. Try again in a minute. |
AI Suggestions (During Setup)
Message | What It Means and What to Do |
Looking for suggestions… | Swivel is still comparing. Restart appears if it's stuck for more than 20 minutes. |
Couldn't look for suggestions / Stopped early | The comparison didn't finish. Fields already created are kept. Click Run again. |
Already looking for suggestions | A look is already running. Wait for it to finish. |
[Field] has been mapped since this suggestion was made | Someone mapped that row directly, so the card no longer applies. |
Already created / Already skipped | Someone else handled the card first, for example in another tab. The message says where the data now goes. |
Another field was just created with the same name. Try again | Rename the card or click Create field again. |
Can't undo | The field already has a value, is used elsewhere, was deleted, or syncing has started. |
Mapping
Message | What It Means and What to Do |
Check this | The row has a warning, such as sensitive data going somewhere unmasked or the same estimate stored twice. |
This choice no longer fits your other defaults or has been removed. Choose again. | A related default or list option changed. Choose a new value. |
A contact keeps the first value it receives here | You mapped per-registration data (such as a meal choice) to the contact. Map it to the registration so each event keeps its own value. |
Changed by someone else — showing the latest | A colleague saved the same row at the same time. Check it and change it again if needed. |
Not saved yet | While syncing, you mapped sensitive data somewhere unmasked. Click Acknowledge and save to keep it. |
Starting and Syncing
Message | What It Means and What to Do |
3 things to decide before syncing starts / Not ready to sync yet | Required setup is incomplete. Click each Take me there link. |
Key rejected / Not syncing: Steep isn't answering / Syncing is overdue | See Connection problems above. |
The import of past events stopped after [x] of [y] events | Click Resume import. |
Not available for every contact or event this field reaches | Some matched contacts or events are a type without the custom field you chose, so nothing was stored for them. |
Troubleshooting and FAQ
Why is the first sync (or Preview first sync) taking a long time?
The first sync reads the last month of registrations from Steep, so it can take 15 minutes or more for a busy firm. A Preview first sync test can take a few minutes, longer if Steep is slow. Both run in the background, and you can leave the page. Later syncs take a few seconds.
What do I do if Steep rejected my key?
The key was mistyped, expired, revoked or belongs to a different Steep account. Copy it again from Steep (Account settings → API keys), in full. During setup, paste it and click Check key. After setup, click Replace key on the Steep page. New registrations wait in Steep until a valid key is in place.
Sync activity says Steep hasn't answered or couldn't be reached. What should I do?
Usually nothing. Swivel retries automatically, and the next successful sync picks up where the last one stopped. If the Integrations card shows Syncing is overdue for a while, contact Swivel support.
Why is a registration in Steep but not in Swivel?
It may not have synced yet. Syncs run every 15 minutes, or click Sync now.
Check Waiting for a decision. It may have failed to save, for example because it has no last name. Correct it in Steep.
Check your Steep time zone. A wrong time zone can cause registrations to be missed.
If it's from before syncing started, it's only imported if you import past events.
If you deleted the contact, event or roster row the sync created, Swivel won't recreate it.
I deleted a contact the sync created. Will it come back?
No. Swivel doesn't recreate contacts, marketing events or roster rows you delete. Registrations that need the deleted record are skipped and noted in the exported sync history.
What if AI suggestions couldn't finish or stopped early?
Click Run again. Everything else in setup works normally, and any fields already created are kept.
Does the AI see my clients' information? Does it cost extra?
No to both. The AI sees only field names and list labels from Steep and your Swivel account. It never sees registrant names, emails, phone numbers or sample values. AI suggestions are included at no extra cost.
Why didn't a value from Steep come through?
It may be a new value or field listed under Waiting for a decision. New values use the field's Any other value mapping. If that's set to never import, nothing is stored until you map the value. New fields aren't stored until you map them.
The custom field may not exist on that contact's or event's type.
If the field already had a value, Swivel doesn't overwrite it.
If it's mapped to the contact, the contact keeps the first value it received. Map per-event data to the registration instead.
Why didn't an automation run for an event?
Automations never run for imported past events, including later status changes on them. Automations run for new leads the sync creates, the same as for leads entered by hand.
A status changed in Steep, but the roster hasn't updated. Why?
Rosters refresh hourly for events in the next 7 days or the last 2 days, and daily for other events until 14 days after they started. After that, rosters aren't refreshed.
Click Sync now to check today's rosters immediately.
If staff changed that roster value by hand, Swivel keeps their change.
Will the same person become two contacts?
Not from Steep. Contacts are matched on Steep's person ID, so a returning registrant is updated. Contacts aren't matched on name, email or phone.
Does Swivel set texting consent from Steep?
No. The sync never sets texting consent, whatever Steep sends. Your staff record consent on the phone record when the contact gives it.
Can my staff use the Steep integration?
Staff users can work with the contacts, marketing events and rosters the sync creates, and their changes are never overwritten. Only account owners and managers can set up, change, export or disconnect the integration.