Say how you want it done. Pathfinder builds it.
The follow-up, the dashboard, the form and the fields behind it. Describe what you want the way you'd explain it to a new hire, and it's built with your people, your tags and your templates. You read it, then you publish.
Build any automation in your CRM just by talking to it.
An automation is follow-up that runs on its own: the welcome email, the paperwork task, the call three days after a seminar. Tell Pathfinder what should happen and when, and it builds every step with your people, your tags and your emails.
If it needs something only your office knows, it asks. Then you publish, and it runs for every household.
AutomationsWant a KPI? Tell Pathfinder what it is and it builds it.
Skylights are the numbers on your dashboard. Any metric or stat you want, from any information inside your CRM: calls made, new households, clients gone quiet, pipeline by stage. Say what you want to see and Pathfinder builds it.
Or pick from 46 that are ready to go. Each one stays up to date on its own.
Dashboard · SkylightsTell Pathfinder what you need to collect. It builds the form.
The hard part of a client form is building it, or knowing what belongs on it when it's something you haven't done before. Talk to Pathfinder about the information you want to gather and it builds the form for you.
Clients open it on their phone, already filled in with what you have on file. Their answers come back to the record for your team to approve.
Form builderYour workflows, from objective to milestones to tasks.
Nothing falls through the cracks. A workflow lays out a whole job the way your office does it: the objective, the milestones along the way, and the tasks under each one. Every task has an owner and a date.
Start it for a client and the right people get the right tasks on the right days. Have a deadline? It counts back from it. An automation can start a workflow too, like when a prospect becomes a client.
Workflow templatesCustom fields build deep, rich client profiles.
Custom fields are where everything you learn about a client lives: their risk tolerance, the grandkids' names, the charity they care about, the boat. The more you capture, the better you understand the people you serve.
Need a field you don't have? Ask Pathfinder for it. An admin approves it, and it's on every client's record.
PathfinderMission Control shows everything your automations are doing.
Every task that's been assigned. Everything that's waiting on someone else. Every automation running right now. It's all on one screen, live.
If one fails, it shows up here and tells you why in plain English. Fix it, retry, and move on. And a Speedbutton starts any automation from the client in front of you.
Mission ControlWatch Pathfinder build one of your automations.
Bring one piece of follow-up your team does by hand today. We'll have Pathfinder build it while you watch, then run it on a sample client.
Names, households and figures on this page are made-up examples, shown to illustrate how Altitude works.What are Automations? Automations is the no-code automation system inside Altitude, the CRM for financial advisors. You describe what you want in plain English and Pathfinder, Altitude's AI assistant, builds it: follow-up automations, Skylight dashboard tiles, client forms and custom fields. Automations can start a workflow template, wait days or weeks for a client, and show every run in Mission Control. You read what was built, then you publish.
Built to be safe with your clients.
It asks before it publishes
Nothing goes live until you say Publish, and it can't publish while anything is still missing.
Changes don't disturb anyone midway
Change an automation and households already partway through finish the way they started.
Do Not Contact always holds
Anyone marked Do Not Contact is skipped, and the skip is logged. A run never fires twice.
You hear about failures
If an automation fails, the people you choose get an alert that says why in plain English.
What can start an automation.
Something changes
A record is created or updated, a field changes, a tag is added or removed, or a relationship is added.
A date arrives
A birthday, an anniversary, an important date coming up, or a client reaching an age such as 73.
Work gets done
A task is completed, or a client form is completed or approved.
The clock
A schedule you set: daily, weekly, monthly or yearly.
A person
Someone presses a Speedbutton on the contact, opportunity or activity in front of them.
Then it can wait
For days or weeks, until a date passes, a field changes, a task completes or another workflow finishes.
Questions advisors ask about Automations.
What are Automations in Altitude?
Automations is the no-code automation system inside Altitude, the CRM for financial advisors. You describe what you want in plain English and Pathfinder builds it: follow-up automations, Skylight dashboard tiles, client forms and custom fields. You read what it built, then you publish.
Do I need to write code or learn a builder?
No. Describe the automation to Pathfinder, by typing or by voice, and it builds the steps on the canvas with your real people, tags and templates. You can also start from a template or drag blocks that read in plain English.
What can Pathfinder build besides automations?
Skylight dashboard tiles, where Pathfinder picks the chart type from your description. Client forms, built by chat or rebuilt from a PDF or image you attach, with every field mapped to the CRM. And custom-field changes, which Pathfinder proposes for an admin to approve.
What can start an automation?
A record being created or changed, a tag being added or removed, a birthday, anniversary or other important date, a contact reaching an age such as 73, a task being completed, a client form being completed or approved, a schedule, or someone pressing a Speedbutton on a record.
Can an automation wait for a client to do something?
Yes. A workflow can pause for days or weeks until a date passes, a field changes, a contact gets a tag, a task completes or another workflow finishes, then pick up exactly where it left off. A wait can also race an event against a deadline, and whichever happens first decides the next step.
What stops a half-built automation from emailing clients?
Pathfinder asks before it publishes, with a Publish or Not now card. Publishing is blocked until every Needs input value is filled. Clients marked Do Not Contact are skipped and the skip is logged, a run never fires twice, and admins get an alert in plain English if an automation fails.
Who can build automations?
Any Altitude user in a firm with Automations turned on, which is every firm. Building with Pathfinder doesn't need Pathfinder+. It does use Pathfinder tokens. Automations and their runs belong to the firm, so the whole team can see them.