Help families act on what your platform delivers.
Your platform manages the official information and workflows. ikr helps families place selected requests alongside the rest of their day, then return to your platform to take the next step.
Extend the usefulness of what you already provide.
Families use your platform within a day that also includes other children, activities and commitments. That wider context is where we want to connect.
A permission deadline can sit beside an activity change or a reminder for another child. The parent sees what needs attention across the day.
The source stays visible. The next step leads to your original form, information or workflow, rather than a duplicate official record.
Evaluate understanding, correct delivery and navigation to the action. Where your platform provides an agreed completion signal, measure that separately.
One request. A clearer route to action.
Publishes the official request.
Brings the next step to the family at a useful moment, with a route back to your platform.
Receives the parent's official response.
A parent sees that a school form is due, opens the original and completes it in your system. The school keeps its existing record. Any status returned to ikr would be part of the integration we agree together.
Illustrative integrationClear roles. A focused connection.
| Your platform | ikr | Together |
|---|---|---|
| Maintains the official record and instructions | Organizes the agreed details in a family context | Choose the use case and participating cohort |
| Handles its own forms, approvals and transactions | Makes the source and next action clear | Agree permissions, data scope and support |
| Confirms completion within its workflow | Uses only the status information agreed for the integration | Evaluate the result before expanding |
Start with one useful connection.
An event, a deadline or a reminder linked to an existing action.
Agree the participants, minimum information, access, support and duration.
Check whether information reaches the right family, stays accurate and leads to the intended action.
Look at family feedback, onward navigation and any agreed completion measure. Decide what is worth building next.
Built on a few shared principles.
Give an update a useful place, rather than simply adding another notification.
A family should know where an instruction came from and how to check it.
Agree what the connection needs, who can access it and how long it is retained.
Evaluate whether the experience helps families and the originating organization.
Detailed engagement analytics for your platform.
See how families engage with what you publish once it reaches them in context: what was seen, when it was acted on, and where the route back to your platform was completed.
How many families saw a request, and how long after publication.
Who followed the route back to your platform, and which requests were completed on time.
Reported at the level agreed for the integration, with the data boundaries you define.
Let's choose a first use case.
Tell us which family-facing workflow you would like to explore. We'll start with a product conversation and a demonstration of ikr. We're inviting initial integration partners.