Site and inquiry terms
These pages explain standard service boundaries. A project begins only after the exact scope, price, exclusions and delivery timing are confirmed in writing.
No automatic agreement
Sending an inquiry form or direct email does not create a project, authorize work or reserve a delivery date. An automated receipt confirms message delivery only. The final written scope and payment request control the engagement.
Japanese Phone Inquiry
A phone-inquiry project covers only the organization, public contact source, up to three factual questions, caller introduction, attempt limit, voicemail rule, report format and delivery timing agreed before payment. JapanOps identifies itself and the purpose of the call. Reservations, bookings, purchases, cancellations, negotiation, adversarial complaints, debt collection, account or identity access, impersonation, employment or personal disputes, mass calling, harassment, deceptive purposes, personal-record requests and legal, medical, tax, immigration, emergency or other specialist matters are excluded. An unanswered, declined or ambiguous point is reported as not confirmed and never becomes permission for another action.
Pilot price and payment
The public US$75–150 range is a typical pilot guide for one organization, up to three factual questions, up to two agreed call attempts and a written fact report. It is not an automatic offer or invoice. The fit review is free. The exact scope, exclusions, attempt limit, price, delivery timing and refund rule are confirmed in writing before payment. Work begins only after that scope is accepted and payment is confirmed. A new organization, changed objective, added question, transaction or other material change requires a new fit review and may be declined or re-quoted; no hidden fee is added automatically.
No connection, cancellation and refunds
If no relevant person is reached after every agreed attempt, JapanOps supplies an attempt log and refunds 50% of the standard service fee. If a relevant person is reached but declines to answer, or confirms that the information is unavailable, that is a completed factual outcome and is reported as not confirmed. The requester or JapanOps may cancel for a full service-fee refund before the first call attempt. After the first attempt, preparation and calling work has begun, so the agreed no-connection or completed-outcome rule applies. Nothing here limits a refund required by applicable law.
Consented recording option
The optional recording add-on is US$35. JapanOps states the recording purpose and begins recording only after the person called explicitly agrees and the organization permits it. Recording is stopped or not made if permission is refused, withdrawn, prohibited by policy or likely to capture sensitive information outside scope. In that case the written-report service may continue and the recording add-on is refunded in full. Any audio is delivered by an agreed private method and JapanOps deletes its copy 14 days after delivery. The requester is responsible for saving an authorized copy and may use it for its internal factual review only; publication, resale, training use, deceptive editing or attribution outside the agreed purpose requires separate permission from affected parties.
Timing, voicemail and callbacks
A requested reply date or time is scheduling information, not a reservation or guarantee. The binding delivery timing is the date and time zone stated in the accepted written scope. The default is no voicemail. JapanOps leaves a brief callback request only when that action and its content were approved in the written scope. A callback received after the project closes does not automatically reopen the scope or create a new charge.
Review-only projects
A standalone review covers only the agreed public or otherwise explicitly accessible path and ends with the written findings and rewrites named in its scope. It does not automatically include implementation or create an obligation to buy a completion project.
Completion projects
A completion project begins only after the exact path, editable non-public surface or client-integrated workflow, approved change set, client dependencies, QA environments, exclusions, price and delivery timing are fixed in writing and payment or a funded milestone is confirmed.
Completion and external blocks
JapanOps marks its scope completed only when every approved in-scope change is present on the agreed non-public or client-integrated surface and passes the named QA environments without an obvious regression on those surfaces. Work awaiting client integration is not completed. Missing required client input, access, returned build or an agreed QA surface may block completion; later client-controlled publication or store review does not.
Client changes and correction boundary
QA compares the returned surface with the approved JapanOps change set. Client-side deviations are reported but are not automatically added to the original scope. Unless the written scope says otherwise, completion includes one initial implementation or integration-ready change set and one QA correction pass for defects or omissions against that approved set; new requests require a separate change agreement.
No outcome guarantee
Findings and rewrites are professional review outputs, not guarantees of ranking, inclusion in AI-generated answers, conversion, installs, retention, revenue or legal compliance.
Implementation and publication
Approved implementation may be included only on the least-privilege non-public surface named in a completion scope, or performed by the client and returned for JapanOps QA. The client separately controls publication, store submission, customer communication, purchases and other live changes. Nothing goes live without the authority defined for that action.
Samples
Material labelled “illustrative fictional example” or “concept sample” is demonstration material. It is not client work, a testimonial or evidence of a commercial result.
Questions
Ask about a boundary before payment by emailing main@kohey-nishi.com.