Sources

Sources are raw inputs such as emails, messages, documents, or notes, or live data via webpage or API. They are not treated as rules or decisions on their own - sources provide background, not direction. Instead, DelegateZero extracts relevant information and incorporates it into its understanding.

When adding a source, a short description or notes explaining what the source represents should be included. This helps DZ understand when and how to use the source.

You might add a source when:

• Pasting an email thread
• Uploading a document
• Providing background material

Here are some examples:

Email thread as behavioral evidence:

This email thread shows how the client responds over time to performance issues, what they focus on, and how much explanation they expect. Use this to calibrate tone and depth in future communications.

From: alex@abccompany.com
To: me@company.com
Subject: January performance concerns

Hey — we noticed traffic dipped in the second half of January and wanted to understand why.
Is this related to the changes we made earlier in the month?

Thanks,
Alex


From: me@company.com
To: alex@abccompany.com

Thanks for flagging. The dip aligns with when we paused paid campaigns mid-month.
Overall organic traffic remained stable, and we're seeing positive trends longer-term.


From: alex@abccompany.com
To: me@company.com

That makes sense. We're less concerned about week-to-week movement and more about whether the broader trend is healthy.
Appreciate the clarification.

Webpage as authoritative reference:

This webpage documents a public service outage. Use it as a factual reference when explaining incidents to customers.

https://status.vendorplatform.com/incidents/2026-01-12

Incident summary:
On January 12, VendorPlatform experienced elevated API error rates for approximately two hours.
The issue was resolved and no customer data was affected.

Internal analysis explaining trends:

This internal summary explains why paid traffic declined over time and how we've discussed it internally. Use it to inform explanations and avoid inconsistent narratives.

Paid traffic overview (Q1):

- Paid campaigns were gradually reduced starting mid-January due to declining ROI.
- Spend was intentionally reallocated toward content and SEO.
- Organic growth partially offset the decline, but total sessions were lower short-term.
- We expect stabilization by late Q2.

Internal consensus:
When explaining this externally, frame the change as a strategic shift rather than a performance issue.
Avoid over-emphasizing short-term dips.

Integration source:

This integration provides analytics data for ABC Company. Use only high-level metrics in client-facing communication.

Integration: Google Analytics
Property ID: UA-123456-7
Access: Read-only

Notes:
- Data stabilizes 48 hours after month end
- Do not reference raw events or experimental metrics externally

When adding a source, start by explaining what the source represents and how it should be used. Then add the content itself.