Support hours
This month's example allowance
Connect the tools you already use. Give clients a branded workspace, turn project context into useful AI outputs and keep your team in control.
Keep your tools. Connect your delivery.
Your project, in view
Illustrative dashboard · synthetic data · configured client summary
This month's example allowance
Support #1042 · Zendesk
We've linked the issue to task #87. The proposed fix is awaiting engineering review.
Reviewed by the agency · saved to this project
Illustrative task board · synthetic data · agency view
Linked development work is with the engineering reviewer.
Code and regression test proposed. Human Git review is still required.
The issue stays open until the change is reviewed and verified.
Illustrative request record · synthetic data · read-only example
This is an example of an existing request, not a form. Nothing can be submitted from this preview.
Integrations, not customer endorsements.
Connect support, repositories, time and conversations to the project. Available capabilities vary by integration and require appropriate configuration.
A branded home for the information your client actually needs. Clear progress, relevant support and reviewed deliverables, without opening up every internal tool.
Bring project information together so clients can understand where things stand, not piece together another email thread.
Follow a support request through its linked development work. Keep the explanation beside the progress.
Choose what belongs in the client view. Check permissions and share reviewed outputs, not unfinished agency drafts.
Bring in supported tools.
Validate access and scope.
Share a reviewed outcome.
Ask across agreed project context. Turn recurring work into defined Jobs, combining AI for interpretation, code for rules and human review for the final call.
Run manually or on an agreed schedule. Keep useful reports and documents alongside the project, once approved.
Examples need supported integrations, configuration and testing. A configured workflow is not a one-click promise.
Example configured Job
Support #1042, linked task #87 and project time.
Explain the checkout issue and proposed fix. Flag that engineering review is still pending.
This week's draft is not published. Approval comes before saving it for the client.
Last week's update was reviewed and saved. This is a separate, new draft.
Run Kilo or OpenCode in configured project environments. Inspect, edit or take over in VS Code in the browser. Your developers own the review, not the agent.
Investigate support #1042. Preserve checkout after an address update and propose a regression test.
The agent asks whether changed shipping rates need reconfirmation. The developer confirms: yes.
refreshShipping(address);
+ preserveCheckoutSession();
+ requestRateConfirmation();Illustrative proposed logic. A developer inspects the change and checks the regression test.
Review the proposed fix in GitHub or GitLab. Check scope, behaviour and tests before deciding to merge.
Task #87 is still awaiting engineering review. No automatic merge is shown here.
Your clients don't need to give up the AI tools they like. Your value is connecting their systems, defining the business rules and taking responsibility for a useful outcome.
meldit connects context, execution and shared outputs. Your agency owns the service and the client relationship.
Useful AI needs more than a prompt. Agree the access, inspect the activity and keep consequential decisions with people.
Our draft partner commitment: client workspace information is not used to create competing sales opportunities. Client invitees are not automatically enrolled in marketing.
Control project and tool access. Validate the client view before sharing.
Inspect execution activity, outputs and audit logs, including work needing attention.
Configure budgets and execution limits. Agree available allowances before activation.
Use supported model providers through your own accounts. Provider usage is billed separately.
Room to connect the work, bring in your team and give clients a clearer view.
Excluding VAT. Draft terms, subject to agreement.
Apply for a guided trialModel usage is billed through your supported provider account. Sandbox, storage and other infrastructure allowances are not yet published.
Trial scope, resource limits and any additional charges must be agreed before trial activation. Proposed rule: no automatic resource overages without your approval.
This offer, allowances and approval rules require confirmation before publication.
Start with a real project. Agree the scope, validate the client view and see what connected work can do for your agency.
Proposed 30-day evaluation.
No automatic billing. Scope agreed first.