One agent layer between operational signals and commercial action.
Vinculo sits between the systems where work already happens and the workflows where commercial action runs. Execute everything the relationship permits. Surface only what requires judgment, approval, access, consent, or human action.
Signal
Approved events arrive from systems where work already happens.
Interpretation
Rules recognize structured triggers. AI can interpret more complex operational context.
Relationship
Vinculo determines which approved commercial relationship is relevant.
Permission + authority
The relationship defines what data may be used, what can be disclosed, what Vinculo may execute automatically, and which actions require employee approval, manager approval, customer consent, or human-only action.
Action + execution
Vinculo executes the permitted commercial step in the existing workflow. If authority is missing, it surfaces only the required decision.
Verification + outcome
Vinculo confirms what actually happened, writes the state back, reconciles failures, and learns from verified outcomes.
What AI does, and what people and rules decide
AI interprets complex customer signals. Relationship rules determine authority; people decide only where required.
- Interpret unstructured and semi-structured partner context
- Synthesize events across delivery, billing, CRM and document metadata
- Map observed changes to candidate customer needs
- Generate human-readable reasoning and evidence summaries
- Which commercial relationships are approved
- Which destinations are eligible for a given need
- Which fields may be shared, and with whom
- Which actions execute automatically and which require approval, consent, or human-only action
- Whether an opportunity already exists, and whether to suppress
Cross-company actions fail. Vinculo preserves what happened, retries what it can, and escalates only the unresolved exception.
Failure detected → preserve completed state → retry or alternate route where allowed → record unresolved state → escalate only if human access, judgment, or action is required.
Decision logic for complex signals
When a need is spread across several operational signals, this is how Vinculo reaches a permitted action
1. Connect to approved partner data
- Read-only access to the systems the partner already uses, such as CRM, delivery, documents, and billing
- Optional, opt-in communication sources, used only as supporting evidence
- Clear limits on what is read, and a record of what was read
2. Customer signal record
- Signals from different systems need to be understandable together.
- Each signal should be tied to the right customer.
- The original source should always be traceable.
3. Trigger recognition and interpretation
- Vinculo recognizes defined operational triggers and can use AI to interpret more complex signals when required
- Evidence is grouped as primary, supporting, or corroborating
- AI interprets customer signals. Relationship rules determine authority; people decide only where required.
4. Need confidence
- How much independent evidence supports the need
- Partners can set their own evidence rules
- Low confidence stops the process before any destination is considered
5. Approved commercial relationships
- Which destination companies are approved.
- What type of need each one can help with.
- What kind of commercial relationship exists.
- What action is allowed.
6. Destination fit
- Is this destination actually a good fit for the need?
- Use Strong / Possible / Weak.
- A real need can still result in no action if the fit is weak.
7. Permissions and partner rules
- What can be shared.
- What executes automatically; what requires employee or manager approval, customer consent, or human-only action.
- Which actions are allowed.
- The partner can override or stop an action.
- Access to data and permission to act are not the same thing.
8. Destination pipeline check
- Check whether the destination already has an active account or opportunity.
- Avoid creating duplicate activity.
- Suppress the action if the opportunity already exists.
9. Prepare and manage the action
- Execute where authorized; prepare only the step that requires human action.
- Track whether it executed, was received, was changed, or stopped.
- Avoid sending the same action twice.
10. Deliver into the partner's workflow
- When a person is required, surface only the missing decision where they already work.
- This could be CRM, email, Slack, Microsoft Teams, or another workflow.
- The employee should not need to monitor a separate Vinculo inbox.
- The delivery method can vary by partner.
11. Send the action to the destination
- Check the destination's existing pipeline.
- Send or create the approved action.
- Get enough outcome information back to know what happened.
- Salesforce and HubSpot are examples of destination systems.
12. Track what happened
- Was the referral accepted?
- Was an opportunity created?
- Did the meeting happen?
- Did the opportunity move forward?
- Tie the outcome back to the original Vinculo action.
13. Learning and suppression
- Capture why a partner approves or dismisses something.
- Turn repeated feedback into clearer rules.
- Hold back similar actions when a partner has already shown they are not useful.
- Explicit partner knowledge can override inferred context.
Data boundary
Applied in one place, not per integration
- Prospect identity
- Partner identity
- Approved need summary
- Approved commercial context
- Partner-approved message
- CRM notes
- Project details
- Source documents
- Communications
- Unrelated customer records
Customer identity can remain inside the signal owner's environment until the applicable relationship rule allows it to move.
One decision, many delivery options
- Partner A → CRM card
- Partner B → Microsoft Teams
- Partner C → email
- Partner D → CRM task
The same Vinculo logic can sit underneath. The delivery method can change based on how each partner works.
Delivery adapts to how each partner already works.
What Vinculo does not require
- No broad CRM access or customer-data warehouse required
- No purchased third-party intent data
- No customer identity moves before the relationship rule allows it
- No invented deal values
- No action taken outside the relationship rules