Tenant portals: what is the service request waiting for?

Received, with a date still to be confirmed

Suppose an office tenant in Building A requests extra weekend cleaning. Under the agreed process for this service, the tenant's nominated budget contact must confirm the request before the property team arranges the work. The request has arrived, but that person has not responded. Meanwhile, the employee who submitted it believes the cleaning is booked for the weekend they specified.

The proposed portal shows that employee the request has been received, confirmation from the nominated tenant contact is pending, and the service has not been scheduled. They can open the message requesting confirmation and follow up with their colleague. The property team sees the same request and who needs to respond, without reconstructing the conversation from separate emails.

When confirmation arrives, it stays with the request. The scheduler can continue making arrangements and record the actual date once agreed. The tenant then sees the update and confirmed timing. A colleague covering for the property manager can also find the response and subsequent arrangements in the same record.

Standard portals already handle requests

Prism lets tenants submit and track work orders. Its product material also describes support for billable work and accounting exports (Prism Work Orders datasheet).

If you already have a portal, start with what the tenant sees after submitting a request. An existing waiting stage and a message currently kept within the property team may be enough. Ask your administrator or vendor whether the agreed confirmation process can be supported in your current setup. A general request-tracking feature does not establish how this particular step works.

Compare the available module, a change of plan or contract terms, and another standard portal, accounting for the work staff still perform outside the system.

When the portal needs a connection to building operations

An integration makes sense when tenant requests arrive in one tool, confirmations return by email, and service scheduling happens elsewhere. Connecting those places could keep the response with the request and return the agreed date to the tenant's view. The maintenance team or contractor could continue working in its existing work-order system.

Consider a custom portal when available products do not provide a practical way to show tenants this information, and property staff regularly copy updates and answer repeated questions. An initial scope could cover one additional service across buildings managed by one team. The project would focus on the path from receiving the request to confirming the appointment.

Each request needs to identify the building and tenant. A contact responsible for the office in Building A should reach that office's request, even if the company also occupies space at another address. The property management team defines who on the tenant's side can see the conversation and who receives the confirmation request. Other tenants do not need access to the case.

If the property manager needs help finding the instructions that apply to a building, our article on a Company Brain for property portfolios covers that question.

Preserve open requests and the decisions behind them

When changing tools, move open requests with their attachments and confirmation messages. A list of requests alone would make it harder for staff to pick up the work. Older cases can remain in an accessible archive; also agree on how you could later export the history from the new portal.

Establish who investigates a date changed in the building's work-order system while the tenant still sees the old one. Your company needs someone to maintain contacts and service procedures, and the connections between systems need ongoing support. For a custom application, discuss code and data ownership and the access another provider would need to take over maintenance. Include those responsibilities when comparing the arrangement with a standard portal.

Connect the tenant view to the property team's work

Through its custom application service, Syntalith can build a view connecting the tenant's request, pending confirmation, and agreed service date to your existing building operations system. Tenants can see what their request is waiting for, while staff keep the conversation with the case instead of repeating updates across channels. Your team supplies the contacts and agreed service process.

Tell us about the last request that prompted another tenant call because they could not tell whether the work was scheduled. Explain where the property manager found the missing response. That example will help establish whether portal configuration is enough or whether you need a connection to email or work scheduling. See Syntalith pricing for information about project billing.