THE DIRECT ANSWER
One chat can make portal work easy. It must keep each login, rule, review, and approval clear.
The lesson comes first
A fast tool is not enough. The team must trust it. One chat can sit in front of many portals. Staff must still see who acts, which source is in use, and what will change.
This is the rule behind MasterlineIQ, or MIQ. One chat should make hard work easy. It should not hide control.
Why I built it
Facilities work lives in many customer and provider portals. Staff check a job. They read notes. They find a file. They post an update or close a step. Each portal has its own screens and rules.
MIQ is Masterline’s internal ChatGPT connector. It gives staff one governed place to read facts and plan the next step. Each source portal still owns its data and rules.
What the connector helps staff do
MIQ can find and sum up work orders, bills, sites, notes, files, and status facts. It can draft updates, bids, bills, check-ins, and closeout notes.
MIQ does not hide where a choice came from. It brings the right facts to staff. It makes the next step clear. It keeps a trail.
A person stays in charge
MIQ can use a provider API when it is ready and allowed. A controlled browser pilot can help when a portal has no good API.
Each worker uses their own ID and company access. Each portal keeps its own limits. MIQ shows a preview before a sensitive write. The worker must then approve it.
What MIQ does not do
MIQ does not bypass a provider’s rules. It cannot grant access. Live work needs a valid login, API access, and test approval from each provider.
That limit is part of the product. A useful tool should say what it can do. It should also say why a step may stop.
Where the rollout stands
Connector builds cover ServiceChannel, Corrigo, Coupa, and ECOTRAK. Controlled browser pilots cover OfficeTrax and 86 Repairs.
More portal work is being prepared. The list is Fexa, fmPilot/CBRE, OpenWrench, Vixxo, SAP Ariba, Cushman & Wakefield, MaintenX, FrontStreet, TrueSource, CLS Facilities, Facilities Marketplace, BOSS, Global Facility Management, and PRS. This list shows the work stage. It does not mean each portal is live.
The point is clear work
One interface should not turn many portals into a black box. It should help staff find facts. It should show the next step, ask for approval, and check the result.
That is the kind of AI I want to build. It should help in the real world. It should be honest about its limits. A person should stay in charge.
ORIGINAL WORKSHEET
The four-step control loop
A safe tool should make each step clear. It should not hide who asked, what will change, or what took place.
- 01 · FindWhat facts does the worker need?Pull the right job, bill, site, note, file, or status from a source the worker may use.
- 02 · PrepareWhat is the next useful step?Draft the update, bid, bill, check-in, or closeout note. Do not send it yet.
- 03 · ConfirmWill this change a source?Show a clear preview. Ask for approval before the change is sent.
- 04 · RecordWhat took place?Save what was asked, approved, done, or stopped. This lets the team check the work.
Original evidence: Tim Yslava’s approved MasterlineIQ build record, reviewed July 29, 2026. Rollout stages are named as builds, pilots, or work being prepared. No customer data, private login, or performance result is included.
See the MasterlineIQ product recordRead the current verified product scope, control model, limits, and rollout state.
↗Four takeaways
- Make the work easier without hiding the source.
- Keep each worker’s identity and access rules in place.
- Show a preview before a sensitive change is sent.
- Save a clear record of what worked, failed, or stopped.