You can now do the same for the two record types that drive the admissions decision: Pre Assessment and VOB. Messages about a pre-assessment or a benefit verification go to the same Slack channel as the Intake Opportunity they belong to, so the whole story for one patient stays in one conversation.
Contents
1. Before You Start
2. Choose Which Fields May Be Sent
3. Create a Workflow for a Pre Assessment or VOB
4. Add the Send Slack Message Action
5. Where Your Messages Go
6. Replies From Slack
7. Frequently Asked Questions
1. Before You Start
You will need:
An administrator account in the CRM.
The Slack integration already switched on, with your Slack workspace connected. If you have not done that yet, follow the Slack Integration setup guide first.
Somebody who can decide which pre-assessment and benefit information your organisation is willing to send into Slack. This is a decision about patient information, not a technical setting — see the warning in section 2.
Access requirements: only CRM administrators can change the Slack settings or build workflows. Anyone can see the resulting messages in Slack, which is exactly why section 2 matters.
If you do not see Pre Assessment or VOB in your Slack settings, or the Send Slack Message action is missing when you build a workflow, your instance has not been updated yet. Contact Dazos support.
2. Choose Which Fields May Be Sent
Go to Settings → Integrations → Slack and scroll to Permitted fields.
You will now see two new sections, Pre Assessment and VOB, alongside the ones you already had.
Each of the two new sections starts with just three fields allowed:
Record type | Fields allowed to begin with |
Pre Assessment | Assessment Title, PAA Type, Assigned To |
VOB | VOB Title, VOB Type, Assigned To |
Everything else is switched off. Nothing clinical, nothing about insurance, and no patient identifiers are sent until you deliberately turn them on.
Click a section to open it. Each field has its own switch — blue means it may appear in a Slack message, grey means it may not. Turn on anything you want your team to see, then click Save.
Important: a Slack channel is visible to everyone in it, and Slack keeps its history. A pre assessment contains presenting problem, substance use history and assessment answers; a VOB contains insurance and benefit detail. Turn on only what your team genuinely needs to see in Slack, and review the list with whoever owns compliance at your organisation before you widen it.
3. Create a Workflow for a Pre Assessment or VOB
Go to Settings → Automation → Workflows and click New advanced workflow. 1. In Module, choose Pre Assessment or VOB. Both now appear in the list.
2. Give the workflow a name that says what it is for, such as Notify Slack when a VOB is verified . 3. Choose when it should run under Trigger Workflow On.
4. Add conditions if you only want it to run in certain cases — for example, only when a VOB reaches a particular status.
Tip: conditions are how you keep the channel readable. A VOB changes many times as an eligibility check runs, so without conditions your team will get a message for every one of those changes. Set a condition for the moment that actually matters, such as verification being completed.
4. Add the Send Slack Message Action
In the Workflow Actions section, click Add Action and choose Send Slack Message.
Fill in the action:
Field | Description | Example |
Action Title | A short name so you can recognise this action later | Post to admissions channel |
Slack Channel | Leave on Automatic unless you want every message from this workflow to go to one fixed channel | Automatic |
Message | What your team will read in Slack. Use the Select list on the right to insert a field | VOB [VOB Title] is now [VOB Type] |
The Select list only offers the fields you allowed in section 2, plus a link back to the record. You will also find fields from the parent Intake Opportunity there, which is useful for saying which patient or opportunity the message is about.
Click Save, then save the workflow.
Tip: always include something that identifies the record — the title, or a field from the parent Intake Opportunity — and the Record URL. Without them, a message in a busy channel tells nobody which patient it concerns.
5. Where Your Messages Go
You do not have to pick a channel. When Slack Channel is set to Automatic, the message goes to the channel for the Treatment Location of the parent Intake Opportunity.
That is worth reading twice, because it is what keeps the conversation together:
A Pre Assessment and a VOB do not have a treatment location of their own for this purpose. The Intake Opportunity they belong to decides where the message goes.
So a pre-assessment, a benefit verification, and the opportunity itself all appear in the same channel.
What happens if something is missing:
Situation | What happens |
The parent opportunity's treatment location has a channel | The message goes to that channel |
The treatment location has no channel yet | A channel is created for it automatically, if you have automatic channel creation switched on |
The parent has no treatment location, or the record has no parent | The message goes to your default channel, and the reason is recorded |
A message is never silently dropped. If it cannot go to the ideal channel it goes to your default one instead.
Tip: if you want one particular workflow to always post somewhere specific — a compliance channel, say — pick that channel in the action instead of leaving it on Automatic. That choice always wins.
6. Replies From Slack
When someone replies to one of these messages in the Slack thread, the reply is saved back into the CRM as a comment, so the conversation is on the record and not only in Slack.
Where the comment appears depends on your CRM:
If the record type shows a Comments panel, the reply is saved on that record — on the VOB or the pre-assessment itself.
If it does not, the reply is saved on the parent Intake Opportunity instead.
The second case exists so replies are never lost. A comment saved on a record type that has no Comments panel would be stored but never displayed, and the person who typed it in Slack would have no way of knowing. Putting it on the parent opportunity keeps it visible.
Every captured reply ends with a line naming the Slack member who actually wrote it, so you can always tell a Slack reply from something typed directly into the CRM.
7. Frequently Asked Questions
Q: We do not want any clinical detail going into Slack. What do we have to do? Nothing. The two new record types start with only their title, their type and the assigned user allowed. Clinical and
insurance fields are off until an administrator turns them on.
Q: Can I stop sending these messages later? Yes. Switch the workflow off in Settings → Automation → Workflows, or switch the whole Slack integration off in its settings. Either takes effect immediately.
Q: Someone turned on a field we should not be sending. What happens to messages already in Slack? Turning the field off stops it appearing in future messages. Messages already posted stay in Slack — Slack keeps channel history, and the CRM cannot remove them. You would need to delete them in Slack.
Q: Our VOB records change constantly. Will this flood the channel? Only if the workflow has no conditions. The workflow's own conditions decide when a message is sent, so set them for the moments that matter rather than every update.
Q: Will a pre-assessment and its VOB end up in different channels? No. Both follow the parent Intake Opportunity, so they land in the same place as the opportunity.
Q: What if a VOB is not linked to an Intake Opportunity? The message goes to your default channel and the reason is recorded, rather than failing.
Q: Does this change anything about the Slack messages we already get for Intake Opportunities, Accounts or Leads? No. Those work exactly as before, including which fields they are allowed to send.
Q: Can a completed VOB close or archive a Slack channel? No, and this is deliberate. The channel is shared with the patient's Intake Opportunity and anything else attached to it, so one finished verification must not close it for everyone else.
Need Help?
If you run into issues:
1. Check that the Slack integration is still switched on and your workspace still shows as connected, in Settings → Integrations → Slack.
2. Check the workflow is switched on and its conditions really match the records you expect.
3. Check the Permitted fields list — a message that arrives looking empty usually means the fields it used are not allowed.
4. Contact Dazos support with the workflow name, the record you expected a message for, and the time it happened, quoting reference CRM-3774.