Loading
Because they run in different systems on different customers. The rollout is a project; the problems it causes are tickets; and nobody joins them until a client meeting where both come up at once.
The account manager then hears about an escalation from the client rather than from the company.
Both read the same company record. A project phase and the tickets raised against it sit on one timeline, so a rollout going badly is visible as ticket volume rather than as a rumour.
Capacity accounts for both: an engineer on a project and an engineer on escalations are the same person, and Loop knows it.
It is not an RMM or a monitoring platform. It does not discover devices or raise alerts — it holds the work and the commercial reality around them.
And it will not resolve the tension between project and support priorities. It makes the trade-off visible, which is where those decisions should be made anyway.
Time logged against project and support work produces cost against each, so a managed-service contract that is quietly unprofitable is visible in the month.
Books bills the project from the sold lines and the contract on its own schedule, from the same record.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
Yes, on the same customer timeline, because Desk writes to the same record.
Yes — one person, one availability picture.
Yes, from Books, both against one customer.
Half an hour on your own numbers is usually enough to say whether Loop is the right place to start.