Focus attention
Match the message to the relevant scope and audience.
Subscriptions & notifications
How do we get the right production issue in front of the right person?
Organize notifications around the event, area and audience, giving teams a practical way to hear about the conditions they are responsible for reviewing.
A practical path from evidence to action
- Publish a conditionDefined event and relevant scope
- Match the audienceProfiles and subscriptions
- Deliver the notificationConfigured channel
- Review and follow upDelivery evidence and team response
Give teams a choice
Use supported channels configured for your organization.
Troubleshoot delivery
Inspect delivery history when a message does not arrive as expected.
More messages do not necessarily mean better awareness.
A useful notification reaches someone who understands the context and owns the next step. IntelliTrack™ separates what is published from who subscribes and how the message is delivered, so your team can configure an intentional notification workflow.
How it works in IntelliTrack™
Define the signal, audience and response.
Choose what matters
Configure the applicable publication, its scope and relevant severity or cooldown behavior.
Connect the people
Use profiles and subscriptions to connect eligible recipients with the events they need to review.
Test the delivery path
Configure the selected channel, trigger a representative event and inspect delivery results. Agree on the operational response outside the message itself.
Illustrative manufacturing scenario
Quality needs a process signal; the next shift needs a summary.
A process engineer wants relevant SPC notifications for an area, while a supervisor wants to know when a shift summary is ready. Separate subscriptions let each team receive the information suited to its responsibility.
Publications and scope
What you can inspectThe event type and area or other applicable filters.
Your team's decisionDecide what should warrant attention.
Profiles and subscriptions
What you can inspectThe configured audience and delivery preferences.
Your team's decisionConfirm the right recipients are included.
Delivery history
What you can inspectRecorded delivery attempts and outcomes.
Your team's decisionInvestigate failed channels or an unexpected absence of messages.
Give the workflow the context it needs.
- Email needs a working SMTP setup. SMS uses your configured Twilio service and recipient consent; Teams and Slack require the applicable webhooks. External services can have their own costs.
- Some publication types depend on enabled Insights or Assist features and on report or summary processing. Confirm the feature behind the message.
- Define the people and procedure for responding. Notifications are an awareness mechanism, not an equipment interlock or a guarantee of delivery.
Practical questions
What to know before you start.
Which delivery channels can we use?
Supported workflows include in-application notifications, email, SMS through configured Twilio service, and Teams or Slack webhooks. Set up and test the channels your organization permits.
Can users choose their own subscriptions?
Signed-in users can manage subscriptions within the supported workflow, while administrators configure channels and relevant audience controls. Evaluate the roles and scope your organization needs.
Can we reduce repeated messages?
Applicable publication settings include scope, severity and cooldown controls. Tune these against a representative event pattern so important messages remain useful.
What happens if a channel fails?
Delivery history helps you inspect attempts and failures. Check service credentials, connectivity and recipient configuration; external delivery cannot be assumed merely because an event was recorded.
Do we need AI for all notifications?
No. Notifications are not inherently AI-based. A notification about an AI-generated shift summary requires that summary workflow, while other publication types depend on their own underlying data and feature configuration.
Start with one event that should reach the right person.
Bring the event, the intended audience and the preferred delivery channel. We can work through scope, subscription and delivery evidence.