Search blocks by description or jump to a page.
Four channel rows with response expectations beside a sample fortnight timeline and a single boundary rule, showing the support layer between calls.
The source for every Portfolio block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
Between Sessions shows that an engagement is a relationship, not a series of billed hours. The left column lists four support channels as ruled rows, each with an icon, a response expectation inline with the name, and a plain description: async questions, voice notes, document review, and a shared session log. The right column pairs a sample fortnight panel, tracing a realistic two week rhythm from live session to margin notes, with a single boundary rule that keeps the layer a steady drumbeat rather than an on call service.
Channels and the fortnight entries each live in their own typed array, so changing the support model or the sample rhythm is edits to a list. The response expectation sits on the same baseline as the channel name and wraps below it on narrow screens, and the two column grid collapses to a single stack on small viewports.
Reach for this block on a coaching page when the offer includes ongoing support and a visitor needs to know what they get on the days no call is booked. The installer swaps the four channels, the response times, the fortnight entries, and the boundary rule to match their real engagement.
A natural flow around it on a Portfolio Pro page:
Before
After
One strong use is the between-session support layer. Other ongoing-relationship layouts:
Tip: the response expectation beside each channel sets the boundary before it is tested, a visitor sees the rhythm is steady, not on demand.