Home hosts two operational sections: the full task hub scoped to the agency's own account, and the callback queue. Tasks created from a deal card carry the builder's name as context, and the follow-up engine files its tasks into the same place.
Also called: my tasks · call back list · reminders · who owes a call
- 1The task hub runs in agency scope, using the platform roster as the assignable people.
- 2Tasks take a day and time and ride the existing reminder pipeline for email, text and push.
- 3Tasks added from a deal card carry that builder as their context label.
- 4The callback queue lists who is owed a call, exactly as the builder-facing one does.
- 5Both sections collapse and remember their state.
Quoted on the page: 'The agency's own task manager — the builders' TaskHub, pointed at org _platform (assign to staff, day + time, email/SMS/push reminders).' The roster module explains what makes it possible: agency staff are exposed 'as a roster the task/notification plumbing can use exactly like a tenant's org members.'
- Agency work had no task system, so reminders were personal habits.
- Callbacks were tracked on paper or not at all.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →