VELORYZ STUDIO / KNOWLEDGE

Studio communication

Accurate project updates, copy standards and promises.

10 — User-facing copy, promises and team communication

Voice

VELORYZ should sound like a capable multidisciplinary team: calm, direct, warm and precise. Avoid wording that makes one named person the point of contact or decision maker inside the public creator. Do not mislead visitors by claiming a large staff, available human chat, instant approval or 24/7 monitoring when those facts have not been verified.

Standard copy for the creator

  • Welcome: “Tell us what you have in mind. One thoughtful question at a time.”
  • Top action: “Continue →”; Review action: “Send my project →”.
  • Budget: “Early planning range”; “Your preferred budget”; “The team will confirm scope, deliverables and a written quotation.”
  • Marketing: “We can discuss a smaller first release, phased delivery or eligible published offers.” Not “Guaranteed reduction.”
  • AI: “Ask VELORYZ Project AI”. Live provider replies labeled “Project AI · Live model”. Model failures labeled “Studio guide · Prewritten”.
  • Review: “Your project outline”; explain that the PDF is an illustrative planning document.
  • Success: “Project submitted successfully”; show the exact server-generated reference.
  • Email: “Check your inbox and spam folder for updates. The team may contact you; the twelve-hour window is not a guaranteed response time.”
  • Portal: “A separate one-time invitation may be sent after your private project workspace is created. Enter that code at /client/.”

Do not say

  • “Your client activation code has been emailed” merely because an enquiry was submitted.
  • “Your project has been approved,” “Price locked,” “Offer automatically applied,” or “AI has confirmed your quote.”
  • “We always reply within 12 hours” unless the business has a verifiable service commitment.
  • “We built the external marketplace template,” “Template license included,” or “Identical CSS” if only an inspiration link is provided.
  • “All copyrights transferred” without a signed agreement and rights assessment.

Team support handoff

For support by WhatsApp/email, ask for the public project reference, not an invitation token, password, CVV, payment credentials or customer data. Explain that contact buttons open the visitor's communication app and do not send a message automatically. Confirm the preferred communication channel only after the visitor submits it.

Content-release checklist

Every published offer must include title, eligible audience, conditions, relevant dates, exclusion details and reviewer approval. Every external template should retain an original source link. Every privacy or ownership statement must be reviewed for factual/legal accuracy. Update UI text, documentation and tests together when these promises change.

Let’s talk
Make your project