The team at Daphnis Labs redefined what’s possible for Urbanface. They delivered a bespoke, animation-heavy website that remains incredibly quick and functional. The…
Help users actinside yourproduct.
A contextual copilot that understands the current screen, selected record and user role.
Current screen
Selected record
User role
Copilot
- 1Suggestion
- 2Preview
- 3Confirm
What Can Users Do Faster?
Explore servicesForm Completion
Report Building
Record Editing
Onboarding Help
Workspace Search
Task Shortcuts
What You Actually Get
- Copilot Interface
- Screen Context Adapter
- Action Schemas
- Preview Components
- Permission Mapping
- Feedback Events
- Product Test Suite
- Integration Guide
- Copilot Interface
- Screen Context Adapter
- Action Schemas
- Preview Components
- Permission Mapping
- Feedback Events
- Product Test Suite
- Integration Guide
Example: Move a Project Milestone.
Step 1 / 6
Open Project
The milestone record is selected
- Open Project
- Request
- Proposed Date
- Preview
- Confirmation
- Saved Record
Worked example · Step 0 of 6
What Does It Take to Build?
Get a custom estimatePilot
- One product screen
- One supported action
- Prototype interaction
- Recommended
Production
- Several product journeys
- Live application APIs
- User feedback collection
Enterprise
- Multiple products or tenants
- Shared design system
- Custom rollout controls
- Ongoing feature development
- Founded in
- 2013
- Projects delivered
- 550+
- Client countries
- 43+
- Global offices
- 3
FAQs
How is this different from a standalone assistant?
A copilot is part of the product interface and can use the current screen and selected records. A standalone assistant has its own workspace and may span several business tools.
Can it fit our existing design system?
Yes. The entry point, conversation or command interface, previews and feedback states can use the product's existing components and interaction patterns.
Does it get access to everything on screen?
It should receive only the context needed for the task. Server-side permissions still apply to reads and writes, even when a record is visible in the interface.
Can users inspect changes before applying them?
Yes. For supported edits, we can show a field-level preview and require confirmation. Reversible actions can also expose undo where the underlying product supports it.
Can we introduce it to a small user group?
Yes. Feature flags and defined entry points can limit an initial rollout. We agree which product events and feedback will inform expansion.
How do we know people find it useful?
Measure completion of the intended task, accepted versus rejected suggestions, corrections and user feedback. Conversation volume alone does not establish usefulness.
Which product task deserves a shortcut?
Bring the screen, its users and one action you want to make easier.
