Relationships
Keep the story, the next touch, and the latest context together.
Keep notes, recent changes, and the cleanest next move close enough that continuity does not depend on your memory alone.
Relationship memory
Keep context close to the next touch.
Search fast, spot quiet relationships, and move the next touch forward without losing the last meaningful interaction.
Start with this relationship
Amber Flores
Northstar Studio
Reply to Amber Flores. The latest message has been waiting since 30 days ago.
Latest saved moment
Client-shared context · Client uploaded three onboarding screenshots and a scope note through the shared link.
Best next touch
Reopen the conversation by referencing Jules from Seabird Partners and offering one simple next step.
After that
Once the first relationship is handled, these are the next touches Brivoly would keep close without turning the page into a wall of equal-weight cards.
Let the rest stay quiet until you need them.
Marcus Chen
Riverbridge Ops
Brivoly is still holding context around Proposal sent with a phased rollout option and lightweight pilot pricing, so this does not need to feel like a cold restart.
Best next touch
Pick back up from the last note you sent and make the reply feel easy.
Priya Nair
Lattice Lane
Reply to Priya Nair. The latest message has been waiting since 31 days ago.
Best next touch
Reopen the conversation by referencing Nina at Harbor Circle and offering one simple next step.
Can wait quietly
These relationships are still in view, but they do not need the same urgency as the first few.
Relationship memory
Amber Flores
Northstar Studio
What matters now
Open with the relationship story, not the status.
Brivoly keeps the latest saved moment, the open loop, and the cleanest next touch together so you can step back in without piecing the story together first.
Latest saved moment
Client-shared context · Client uploaded three onboarding screenshots and a scope note through the shared link.
Open loop
Could you tighten the recap and send two possible times for next week?.
Best next touch
Reply while the new client context is still fresh and tie it back to the last thread.
Latest client-shared context
May 17, 2026, 12:24 PM · Client uploaded three onboarding screenshots and a scope note through the shared link.
Jump into the story
Relationship read
stale · Discovery
Best channel
Point person
Ada Lovelace
Last meaningful interaction
May 12, 2026, 3:24 PM
Why now
Reply to Amber Flores. The latest message has been waiting since 30 days ago.
Brivoly nudge
Reply while the new client context is still fresh and tie it back to the last thread.
Gentle re-entry
Reopen this relationship without sounding abrupt.
Brivoly is surfacing a low-pressure path back in so you do not have to reconstruct the opening from scratch.
Why now
30 days ago the client shared new context, which gives you a natural way back in.
Why it can still land
There is still a warmer path here through Jules from Seabird Partners.
Best re-entry
Reopen the conversation by referencing Jules from Seabird Partners and offering one simple next step.
Starter line
Quick angle: "Wanted to follow up on the introduction from Jules from Seabird Partners and make the next step easy."
If it stays quiet
If this lands softly but does not reopen, come back through Jules from Seabird Partners instead of forcing a colder follow-up.
Keep this relationship warm
Warm intro source
Jules from Seabird Partners
Next milestone
annual planning window · Jun 2
referral
May 17, 2026, 11:24 AM
Referral reminder
Send Jules from Seabird Partners a quick update before this introduction cools down.
Story spine
Read the relationship in one pass before drafting.
This is the shortest route through what happened, what shifted, what still needs attention, and where the next note should begin.
What happened
Client-shared context · Client uploaded three onboarding screenshots and a scope note through the shared link.
What changed
New since your last touch: Could you tighten the recap and send two possible times for next week?
What still needs attention
Could you tighten the recap and send two possible times for next week?.
Where the next note starts
Reply while the new client context is still fresh and tie it back to the last thread.
Recent shifts
See what actually changed before you write the next note.
Brivoly keeps the freshest thread movement, client-shared context, and saved notes in one short run so you can enter the relationship story at the right moment.
Client-shared context
May 17, 2026, 12:24 PM
Client uploaded three onboarding screenshots and a scope note through the shared link.
call · phone
May 12, 2026, 3:24 PM
Discovery call completed. Timing and scope were positive, but the recap needs to be tighter.
inbound · email
May 9, 2026, 3:24 PM
Inbound request mentioned spreadsheet-heavy client onboarding and missed follow-ups.
Relationship memory
What matters
Client uploaded three onboarding screenshots and a scope note through the shared link Discovery call completed. Timing and scope were positive, but the recap needs to be tighter
Context on hand
Interested, but waiting on a clearer summary of timeline and scope.
Recent upload context
30 days ago new client context came in through the shared upload link: Client uploaded three onboarding screenshots and a scope note through the shared link.
Reply while the new client context is still fresh and tie it back to the last thread.
Meeting prep from fresh context
Latest client-sent context: Client uploaded three onboarding screenshots and a scope note through the shared link. Best use of it right now: Reply while the new client context is still fresh and tie it back to the last thread. The last meaningful discussion centered on Client uploaded three onboarding screenshots and a scope note through the shared link.
Key moments
The moments most likely to shape the next touch.
Client-shared context
May 17, 2026, 12:24 PM
Client uploaded three onboarding screenshots and a scope note through the shared link.
call · phone
May 12, 2026, 3:24 PM
Discovery call completed. Timing and scope were positive, but the recap needs to be tighter.
inbound · email
May 9, 2026, 3:24 PM
Inbound request mentioned spreadsheet-heavy client onboarding and missed follow-ups.
Client-shared history
Keep the client’s updates attached to the relationship story.
Screenshots, whiteboard photos, and handoff notes stay visible here so the next reply can start from what the client actually sent, not from memory alone.
Client-shared context
shared linkLatestMay 17, 2026, 12:24 PM
Client uploaded three onboarding screenshots and a scope note through the shared link.
Use this in the next touch
Reply while the new client context is still fresh and tie it back to the last thread.
Full timeline
Read the relationship story before you write the next note.
The timeline is the running memory of what happened, what changed, and what Brivoly thinks matters now.
client-shared context
shared linkMay 17, 2026, 12:24 PM
Client uploaded three onboarding screenshots and a scope note through the shared link.
call · phone
May 12, 2026, 3:24 PM
Discovery call completed. Timing and scope were positive, but the recap needs to be tighter.
inbound · email
May 9, 2026, 3:24 PM
Inbound request mentioned spreadsheet-heavy client onboarding and missed follow-ups.
Suggested next note
Draft the next note without starting from zero.
Brivoly uses the latest context, suggested next touch, and your saved business profile to suggest a message you can edit before sending.
Sent from
Sender: Fallback defaults
Ways to say it
Pick the message shape that fits this moment, then edit before sending.
Keep the memory current
Keep notes light. This is here to preserve context, not create more work.
Why Brivoly feels lighter
Brivoly remembers relationships so freelancers do not have to.
- Every note, reminder, and suggested message should lower mental overhead instead of adding admin.
- Brivoly should help you stay warm, responsive, and top-of-mind without more software work.
- The goal is continuity and follow-through, not status management.