codeofwhisper
Last updated: May 22, 2026
These terms explain how support with codeofwhisper is scoped, booked, delivered, adjusted, and closed.
Where consumer withdrawal rights may apply, the separate Withdrawal Information for Consumers explains the relevant process in plain language.
These Service Terms explain how support with codeofwhisper works before paid support begins.
They define how collaboration is structured, how support is scoped, how booking and support workflows operate, and what both sides can reasonably expect throughout the support process.
codeofwhisper is designed around calm, practical, operationally focused support. These Terms are not meant to feel aggressive or overly complex. They exist to make expectations, responsibilities, and boundaries easier to understand.
Because digital, technical, organizational, and workflow-related situations can vary significantly, support is structured around agreed scope, operational visibility, and the support format recommended during inquiry, discovery, and clarification.
These terms work together with:
the website
service descriptions
scoped recommendations
booking information
support summaries where applicable.
These terms apply before paid support begins and continue throughout the agreed support scope and collaboration. By proceeding with booking, payment, or active support, the client acknowledges and agrees to the applicable terms in effect at that time.
codeofwhisper provides remote operational support designed to help individuals, freelancers, small businesses, and digital operators navigate technical, organizational, workflow-related, and operational challenges more clearly and sustainably.
Support may include:
guidance
troubleshooting assistance
workflow clarification
implementation assistance
digital organization support
AI workflow assistance
website and technical workflow support within the agreed support scope and selected support format.
Support is scoped, not unlimited. The support format, pacing, implementation depth, and focus are based on the information available during inquiry, discovery, clarification, and recommendation.
Because tools, systems, workflows, and technical conditions can vary, recommendations and implementation decisions are based on the visibility and access available at the time.
codeofwhisper may assist with guidance, troubleshooting, organization, implementation, simplification, and operational improvement within the agreed scope of support. However, support does not automatically include indefinite operational ownership, ongoing maintenance responsibility, emergency response services, enterprise-level managed services, or unlimited future support outside the agreed collaboration structure.
Support is intended to provide practical guidance, structure, and realistic progress. Specific outcomes, technical results, timelines, platform behavior, third-party systems, and operational conditions can vary and are not guaranteed.
codeofwhisper uses a structured support process designed to create clearer operational understanding before paid support begins.
Support typically begins with:
inquiry
clarification
discovery
operational review before a support recommendation is made.
The purpose of this process is to better understand the situation, identify the likely operational scope, evaluate the most suitable support format, and determine a realistic and sustainable next step before booking or implementation begins.
Discovery and clarification are intended to support responsible operational evaluation and support recommendation. They are not intended to function as unlimited free consulting, deep unpaid troubleshooting, or open-ended implementation planning before support has been booked.
Support may be provided through different formats depending on the operational situation, scope, pacing requirements, implementation depth, and collaboration needs involved. These formats may include:
Guided Support
Async Guidance
Done-For-You Operational Support
phased or smaller-scoped support approaches where appropriate.
Different support situations may require different collaboration structures. Some situations are manageable through focused guidance or clarification, while others may require phased implementation, narrower operational focus, or additional support cycles over time.
Support recommendations are based on the information, operational visibility, access, and clarity reasonably available during inquiry, discovery, and clarification. Recommendations are intended to create a responsible operational starting point, not a guarantee that every issue, dependency, blocker, or hidden complexity has already been identified before active support begins.
This structure helps keep expectations clear, scope manageable, and support easier to follow for both sides.
Inquiry, clarification, and discovery exist to create enough understanding to recommend a realistic support direction before paid support begins.
The purpose of discovery is to better understand:
the operational situation
the likely problem area
relevant workflows, systems, tools, or environments
the probable scope of support
the most suitable support format or next step.
Discovery and clarification are intended to support responsible operational evaluation and scoped recommendation. They are not intended to function as unlimited free consulting, deep unpaid troubleshooting, full implementation planning, open-ended technical investigation, or complete operational diagnosis before support has been booked.
Support recommendations are based on the information, visibility, access, operational context, and clarity reasonably available during inquiry, clarification, and discovery. Recommendations are intended to define a responsible operational starting point based on the situation as it reasonably appears at that time.
Because digital, technical, organizational, and workflow-related situations can vary significantly, additional complexity, hidden dependencies, undocumented systems, implementation blockers, operational constraints, or broader structural issues may sometimes become visible only after active support, implementation review, or deeper operational investigation begins.
For this reason, support recommendations, scope decisions, implementation expectations, pacing estimates, and operational direction may sometimes require reassessment, clarification, narrowing, phasing, or adjustment as additional operational visibility becomes available.
The goal is to define a responsible starting point before active support begins.
Support is provided within the operational scope agreed during inquiry, discovery, clarification, recommendation, and booking.
The agreed support scope defines the primary operational focus of the collaboration. Scope may include:
specific operational problems
defined workflows
implementation areas
organizational goals
technical systems
support priorities
agreed implementation tasks depending on the selected support format and operational situation involved.
The purpose of scope is to support:
clearer operational direction
healthier collaboration boundaries
more realistic pacing
manageable implementation flow
calmer and more sustainable support delivery.
Support should remain reasonably aligned with the agreed operational scope throughout the support process. Newly introduced requests, unrelated operational issues, materially expanded implementation areas, or broader restructuring needs may require:
clarification
reassessment
phased continuation
narrowed focus
separate support scope
additional support cycles depending on the operational situation involved.
Not every situation is best handled through one large scope. Smaller support steps, phased implementation, or a narrower focus may be more realistic.
Scope recommendations and operational boundaries are intended to support:
implementation clarity
operational manageability
healthier pacing
more realistic expectations
sustainable collaboration structure rather than unlimited operational expansion during active support.
Scope definition is not meant to restrict reasonable collaboration. It keeps the work focused, understandable, and realistically manageable.
codeofwhisper offers different support formats depending on the scope, complexity, timing, and type of support needed.
Guided Support
Guided Support is scheduled live support, generally up to 90 minutes unless otherwise agreed in writing. It may include live chat-based collaboration, optional screen sharing, troubleshooting guidance, workflow walkthroughs, and implementation clarification.
Guided Support is intended for focused, session-sized support. If broader implementation work or a larger scope becomes visible, codeofwhisper may recommend another session, phased continuation, narrower focus, Done-For-You Support, or a revised support structure.
Async Guidance
Async Guidance is structured written support over a bounded asynchronous support cycle. Unless otherwise agreed in writing, it includes up to 5 structured operational exchanges over a maximum 14-calendar-day support window.
One exchange generally means one structured client communication and one structured operational response.
Administrative or preparation communication does not count toward async exchanges. This may include scheduling messages, intake clarification, document requests, access/setup coordination, or preparation instructions.
Async Guidance is not unlimited messaging access, instant-response support, continuous live troubleshooting, or indefinite asynchronous collaboration.
The client remains responsible for implementation execution, operational actions, and applying the guidance provided unless separate implementation support has been explicitly agreed.
Async Guidance may conclude earlier if the agreed scope has been reasonably completed, implementation direction has been sufficiently delivered, or clarification is no longer operationally necessary.
Async Guidance automatically closes when the agreed operational scope has been reasonably addressed, 5 exchanges have been completed, or the 14-calendar-day support window expires, whichever occurs first operationally.
Any future continuation after closure is treated as a new operational support cycle requiring new evaluation before continuation.
Done-For-You Support
Done-For-You Support is scoped implementation-oriented support performed within the agreed operational boundaries. Depending on the scope, it may include implementation work, workflow setup, operational restructuring, deployment assistance, technical configuration, or other agreed implementation tasks.
Done-For-You Support does not function as indefinite operational responsibility, ongoing maintenance, permanent technical stewardship, unlimited implementation work, or open-ended operational delegation.
All Done-For-You work must remain clearly scoped, operationally defined, realistically manageable, and bounded by agreed deliverables and implementation direction.
Done-For-You Support includes a 7-day post-delivery adjustment window after operational delivery has been reasonably completed.
The adjustment window is for minor corrections, clarification, stabilization, and alignment within the agreed scope only. It does not include major redesigns, unrelated implementation requests, significant workflow expansion, new operational scope, or indefinite revision cycles.
Any work beyond the originally agreed scope may require new scoped support, phased continuation, or new operational evaluation.
Once the adjustment window expires, the Done-For-You support cycle is considered operationally closed. Any future continuation after closure is treated as a new operational support cycle requiring new evaluation before continuation.
codeofwhisper support is designed around:
structured collaboration
calmer operational pacing
focused communication
sustainable support handling
operational clarity
rather than continuous reactive communication or unlimited support access.
Communication throughout the support process should remain:
reasonably organized
operationally focused
manageable
collaborative
respectful of pacing and operational structure.
Support communication may involve:
operational review
implementation evaluation
troubleshooting analysis
internal preparation
technical clarification
workflow organization
before a structured response is provided.
For this reason, support communication should not be interpreted as:
instant-response availability
continuous live messaging access
unlimited reactive troubleshooting
indefinite operational escalation
unrestricted ongoing communication outside the agreed support structure.
Response pacing may vary depending on:
operational workload
implementation complexity
active support volume
scope clarity
required operational review
technical evaluation requirements.
Some responses may reasonably require additional operational review time before guidance, recommendations, implementation direction, or clarification can responsibly be provided.
Clients are encouraged to:
consolidate related questions
organize updates clearly
provide relevant operational context
reduce fragmented rapid-fire communication across multiple separate messages
where reasonably possible.
Structured communication helps support:
clearer operational handling
healthier collaboration pacing
reduced communication fragmentation
more manageable troubleshooting flow
calmer and more sustainable support delivery.
Communication access and operational interaction remain bounded by:
the agreed support format
the agreed operational scope
active support cycle limits
operational pacing realities
scheduling structure where applicable.
Operational work, implementation review, troubleshooting analysis, technical preparation, or internal evaluation may sometimes occur between communication updates. Periods of reduced outward communication do not necessarily indicate inactivity, abandonment, or unreasonable delay where operational work is actively being reviewed, organized, evaluated, or prepared internally.
The purpose of these communication boundaries is not to create unnecessary distance or operational rigidity, but to support:
healthier operational rhythm
more thoughtful support handling
clearer collaboration structure
reduced operational overwhelm
calmer and more sustainable support delivery
for both sides throughout the support process.
Support works best when both sides have the information, access, preparation, and cooperation needed to handle the agreed scope responsibly.
The client is responsible for providing information that is reasonably accurate, relevant, and complete based on what they know about their situation. This may include:
operational context
relevant tools, platforms, systems, or workflows
known issues or previous attempts to solve the problem
access limitations
deadlines or timing constraints
important dependencies
relevant business, project, or technical context.
If important information is missing, inaccurate, delayed, unclear, or withheld, support quality, pacing, recommendations, implementation direction, and operational outcomes may be affected.
Clients are responsible for participating reasonably in the support process. Depending on the selected support format, this may include:
responding to clarification questions
preparing requested materials
attending scheduled sessions on time
providing necessary access or permissions
reviewing guidance or recommendations
carrying out agreed client-side actions
confirming relevant operational details
communicating blockers or changes that may affect the agreed scope.
For Guided Support and Async Guidance, the client remains responsible for carrying out their own operational actions unless separate implementation support has been explicitly agreed. Guidance-oriented support may provide clarification, troubleshooting direction, workflow analysis, implementation guidance, and structured recommendations, but it does not automatically transfer execution responsibility to codeofwhisper.
For Done-For-You Support, the client remains responsible for providing the access, information, approvals, materials, and operational context reasonably needed for the agreed implementation work to be carried out. Delays in access, missing information, unclear approvals, or unstable operational environments may affect delivery timing, implementation flow, or support feasibility.
Where support involves websites, hosting, cloud systems, databases, spreadsheets, automations, integrations, deployments, restructuring workflows, or other technical or operational environments, the client is responsible for maintaining appropriate backups, export copies, recovery access, account access, and retention of important data where reasonably possible.
codeofwhisper may recommend backups, staged handling, access clarification, or additional caution before higher-risk implementation work begins. However, clients remain responsible for ensuring that important files, systems, accounts, credentials, data, and operational materials are retained, recoverable, and accessible where needed.
Clients should not provide unnecessary sensitive information, passwords, private credentials, personal data, or unrelated access unless specifically requested and operationally necessary for the agreed scope. Access should remain limited to what is reasonably required for the support being provided.
If the client changes goals, introduces new priorities, expands the request, delays required participation, or changes the operational environment during active support, the agreed scope, pacing, support structure, or implementation direction may require reassessment.
The purpose of client responsibilities is not to shift all operational burden onto the client, but to support clearer collaboration, safer implementation handling, healthier pacing, more realistic expectations, and more sustainable support delivery for both sides.
Digital, technical, and operational environments may contain unpredictability, hidden complexity, undocumented dependencies, third-party behavior, platform instability, sync issues, deployment conflicts, access limitations, outdated tooling, or other conditions outside reasonable visibility or control.
This may be especially relevant when support involves:
websites
hosting
cloud systems
databases
spreadsheets
automations
integrations
deployments
restructuring workflows
implementation-heavy operational work.
codeofwhisper will aim to operate carefully, responsibly, and with reasonable operational judgment based on the information, access, visibility, and environment conditions reasonably available at the time support is provided.
Where implementation work appears higher-risk, codeofwhisper may recommend:
staged implementation
testing or non-production environments
phased changes
additional review before proceeding
reduced implementation scope
pausing or delaying implementation until the environment is clearer.
Support cannot guarantee that every environment will behave predictably, that third-party systems will remain stable, that rollback or recovery will always be possible, or that hidden environmental issues will not emerge during support.
Clients remain responsible for maintaining appropriate backups, recovery access, account security, system safeguards, and retention of important operational data before, during, and after support, especially where support involves live systems, business-critical files, accounts, websites, databases, automations, or third-party platforms.
If an environment appears unusually unstable, unclear, fragmented, undocumented, or higher-risk, codeofwhisper may pause, narrow, delay, restructure, or reassess the support approach before continuing.
Any access, permission, or environment visibility requested by codeofwhisper should remain connected to the agreed support scope and limited to what is reasonably needed for the support being provided.
The purpose of this approach is to support safer implementation handling, calmer operational decision-making, more realistic expectations, and responsible support delivery when working with digital, technical, or operational systems.
Support is booked after inquiry, clarification, discovery, and support recommendation have created enough operational clarity to define a suitable next step.
Before booking, the client should receive or have access to relevant information about:
the recommended support format
the agreed operational focus
the intended support scope
pricing
scheduling where applicable
preparation requirements where applicable
relevant Service Terms
withdrawal or early-start information where applicable.
Booking access is generally provided after a support recommendation has been made. codeofwhisper does not use public pressure-based booking flows or aggressive sales-style scheduling. Booking and payment access are intended to support a calm, private, and informed decision by the client.
A support booking is considered operationally confirmed only when:
payment has been completed
the required calendar booking has been successfully scheduled where applicable
required confirmations or acknowledgements have been completed where applicable.
Payment alone does not automatically begin active support. Active support begins only when the required booking, preparation, scheduling, access, and confirmation steps have been completed as applicable to the selected support format.
Payment confirms access to the agreed scoped support cycle or support format. It does not create unlimited support access, indefinite operational responsibility, open-ended troubleshooting, or support beyond the agreed scope.
If the booked support no longer matches the agreed recommendation, operational scope, client needs, preparation status, or implementation reality, codeofwhisper may pause, clarify, reschedule, narrow, or reassess the support structure before active support begins.
Where preparation, access, client information, or required confirmations are missing, incomplete, delayed, or unclear, support delivery may be delayed, rescheduled, or reassessed until the necessary operational readiness is reasonably in place.
The purpose of the booking and payment process is to support clearer expectations, calmer scheduling, responsible preparation, informed client commitment, and sustainable support delivery before active work begins.
Where the client is acting as a consumer, statutory withdrawal rights may apply depending on the situation, location, service type, and applicable law.
codeofwhisper will provide separate Withdrawal Information for Consumers before booking or payment where consumer withdrawal rights may apply. That information explains the possible 14-day withdrawal period, how withdrawal can be made, and what happens if support begins before the withdrawal period has ended.
If support is scheduled to begin within 14 days of contract or payment confirmation, and the client is acting as a consumer, codeofwhisper must receive explicit early-start confirmation before support begins.
Early-start confirmation means the client expressly requests that the agreed support begin before the withdrawal period has ended.
If the required early-start confirmation is not provided, support will not begin during the withdrawal period. Booking may be delayed until the withdrawal period has ended, the client may choose a later support start date, or the client may choose not to proceed.
No early-start confirmation means no early support start.
If the agreed service is fully completed after valid early-start confirmation, the withdrawal right for that completed service may end where legally applicable.
If the client withdraws after support has already started, payment may still be required for the portion of support already provided where legally applicable.
This process is intended to support consumer protection, clear booking records, and fair expectations before support begins.
Rescheduling and cancellation are handled according to the selected support format, the timing of the request, whether support has already started, and any applicable statutory withdrawal rights or early-start rules.
Cancellation handling is not intended as a punishment. It reflects reserved capacity, preparation time, operational review, support availability, work already performed, and payment processing realities, subject to any applicable statutory withdrawal rights.
Guided Support is tied to a scheduled live support session.
Rescheduling requests made 48 hours or more before the scheduled session may usually be rescheduled without consequence.
Rescheduling requests made less than 48 hours before the scheduled session may reduce the available rescheduled session time by up to 25% because preparation time and scheduling capacity may already have been reserved, where legally permitted and subject to any applicable statutory withdrawal rights.
Cancellation requests made 48 hours or more before the scheduled session may be handled through either:
future support credit tied to the original support scope or project
or refund handling minus a 25% operational reservation retention, where legally permitted and subject to any applicable statutory withdrawal rights.
Future support credit expires after 90 calendar days if unused, unless otherwise agreed in writing.
Failure to attend a scheduled Guided Support session without communication may be treated as a no-show, and the session may be treated as used, where legally permitted and subject to any applicable statutory withdrawal rights.
Late arrival does not extend the scheduled session. Guided Support ends at the originally scheduled end time unless codeofwhisper expressly agrees otherwise.
Async Guidance reserves an asynchronous support window, operational review capacity, written response preparation time, and support attention.
Async Guidance begins from the confirmed Async start date, or from payment confirmation if immediate start has been agreed and any required early-start confirmation has been provided.
Before Async Guidance has started, cancellation may be handled according to applicable withdrawal rules, payment processing realities, and any preparation already completed.
Once Async Guidance has started, cancellation does not automatically create a full refund.
Cancellation after Async Guidance has started may involve, where legally permitted and subject to any applicable statutory withdrawal rights:
a 15% base cancellation retention
plus the value of any support already provided, used, prepared, or materially worked
Unused exchanges do not automatically create partial refunds once the Async Guidance cycle has started, where legally permitted and subject to any applicable statutory withdrawal rights.
Client delay, non-response, fragmented communication, delayed follow-up, missing materials, or missing clarification does not automatically pause or extend the agreed Async Guidance window.
Async Guidance closes when:
the agreed operational scope has been reasonably addressed
5 structured exchanges have been completed
or the 14-calendar-day support window expires, whichever occurs first operationally
Any continuation after closure may require a new operational evaluation and a new support cycle.
Done-For-You Support may involve preparation, review, setup, planning, implementation work, reserved project capacity, partially completed deliverables, or completed scoped work.
Done-For-You Support begins from the confirmed project start date or implementation window, or earlier if immediate start has been agreed and any required early-start confirmation has been provided.
Before Done-For-You Support has started, cancellation may be handled according to applicable withdrawal rules, payment processing realities, and any preparation already completed.
Once Done-For-You Support has started, cancellation does not automatically create a full refund.
Cancellation after Done-For-You Support has started may involve, where legally permitted and subject to any applicable statutory withdrawal rights:
a 15% base cancellation retention
plus the value of any work already completed, partially completed, prepared, reviewed, started, or materially worked
Where the support scope contains several scoped items, refund or credit handling may consider the value of the relevant scoped items and the work already performed, where legally permitted and subject to any applicable statutory withdrawal rights.
Once Done-For-You Support has been delivered, the support cycle is generally handled through the applicable post-delivery adjustment window rather than ordinary cancellation.
The adjustment window is intended for reasonable clarification, minor corrections, stabilization, or alignment within the agreed scope. It is not a cancellation period for completed scoped work, subject to any applicable statutory withdrawal rights.
Client delay, missing materials, missing access, delayed approval, unclear communication, or non-response is not the same as voluntary cancellation.
Client delay or non-response does not automatically create refund entitlement, support window extension, additional exchanges, automatic continuation rights, or indefinite project availability, where legally permitted and subject to any applicable statutory withdrawal rights.
If support cannot continue because required client input is missing, the matter may be paused, limited, closed, or reassessed according to the relevant support format.
Once the agreed support has been completed, delivered, used, or closed according to the selected support format, the matter is no longer treated as a normal cancellation.
After completion or delivery, the applicable process may involve clarification, correction of agreed-scope issues where appropriate, post-delivery adjustment handling, closure, new scoped support, phased continuation, or a new support request.
Refunds, where applicable, may be affected by payment processing fees, platform fees, transaction fees, currency conversion fees, or other non-recoverable payment costs, where legally permitted.
This does not reduce statutory consumer withdrawal refunds where different mandatory rules apply.
Outside statutory consumer withdrawal refunds, codeofwhisper is not expected to refund more than the amount actually received or recoverable after payment processing realities.
codeofwhisper provides support with reasonable care, operational judgment, and attention to the agreed scope, based on the information, access, visibility, and environment conditions reasonably available at the time support is provided.
Support is intended to help clarify, guide, troubleshoot, improve, implement, or stabilize agreed operational matters. It does not guarantee that every system, platform, workflow, account, tool, website, automation, integration, or third-party service will behave predictably or remain free from interruption, conflict, error, data loss, or hidden complexity.
Where support work directly causes an issue within the agreed scope, codeofwhisper will review the matter and, where appropriate, make reasonable efforts to correct the issue within the original support context.
However, codeofwhisper is not responsible for wider system effects, indirect losses, business interruption, lost profit, lost opportunity, reputational loss, data loss, third-party platform behavior, hidden dependencies, pre-existing environmental instability, or issues outside reasonable operational visibility or control, except where responsibility cannot legally be limited.
Clients remain responsible for maintaining appropriate backups, recovery access, account ownership, system safeguards, export copies, credentials, and retention of important operational data before, during, and after support.
Where legally permitted, any financial liability of codeofwhisper is limited to the amount paid by the client for the specific support service giving rise to the issue.
Nothing in these Terms limits or excludes liability for intent, gross negligence, injury to life, body, or health, or any mandatory statutory liability that cannot legally be limited or excluded.