Service connections, offerings, and agreements

The service network connects two Companies directly. A connection only expresses recognition; regular work handoffs also require an active offering and a directional agreement.

Availability: Company only; requires Manage service network. Level: Advanced.

Purpose

Use the network to agree which services a provider offers, how work enters its operation, which data the client may share, and whether later subcontracting is allowed.

Create a connection

1. Send an invitation to the verified email of an owner or administrator of an existing Company.
2. The result message is always generic and never confirms whether the account exists.
3. The recipient opens the link within 14 days and accepts or rejects it.
4. The source can withdraw a pending invitation. Either party can terminate an active connection with a reason.

There is no directory. Each Company sees only direct connections, never its neighbors' connections.

Publish an offering

The provider defines a Spanish and/or English name, description, category, manual or automatic acceptance, subcontracting permission, receiving role, and entry point. An active offering requires report type and urgency; entry chain and line are optional.

Agree on service

1. On an active connection, the client proposes an agreement using one or more active provider offerings.
2. For each offering it can adjust acceptance, shareable data—details, reference, contact, equipment, and attachments—subcontracting, and status.
3. It adds Spanish and/or English terms.
4. The provider accepts or rejects. Either party can later terminate with a reason.

Rules and effects

• An agreement is directional: Client → Provider. The reverse direction needs another agreement.
• Only one current agreement can exist per direction.
• A connection alone never authorizes handoffs.
• Ending a connection or agreement prevents new handoffs and cancels pending ones; already accepted work continues until completed or explicitly canceled.
• Invitation, connection, and agreement history is preserved.

Required and optional information

Required: email for a connection; at least one name, acceptance mode, type, and urgency for an active offering; connection and offering for an agreement. Optional: translations, description, category, chain/line, terms, shared categories, and subcontracting.

Practical example

Company A connects with Laboratory B. B publishes “Specialized diagnosis” with manual acceptance. A proposes an agreement allowing details and equipment but not contact or subcontracting. B accepts, and A can now hand off reports under those conditions.

Current limits

• A regular invitation works only with an already registered Company; use a Related company to onboard a new one.
• There is no global search, recommendation system, or transitive visibility.
• A connection shares no historical data and creates no work.
• Ending a relationship does not erase history or automatically cancel accepted work.