Draft a Kannada reply from the facts you have

Specify the audience and the language of the answer

For a customer-service reply, supply the customer question, the applicable policy and any approved Kannada terminology. You can write the instruction in English and explicitly request the customer-facing reply in Kannada. The language of your brief and the language of the final answer are separate choices.

Prompeteer recognizes Kannada script in the Create input. That helps identify the input language; it does not establish fluency, dialect suitability or factual accuracy. Prepare the instruction in Create, then run it with the authorized source material in ChatGPT or your chosen tool.

• Audience: an existing customer, a first-time buyer or an internal teammate.
• Register: state whether the reply should be formal, conversational or based on an approved example.
• Source: identify the policy version and the part relevant to this question.
• Terminology: supply the approved glossary and any words that must remain unchanged.

Decide what should not be translated

A fluent sentence can still change a commitment. Preserve customer names, product names, order identifiers, amounts and dates as supplied unless you explicitly approve a different representation. Ask the reviewer to compare them with the original, including units and time zones.

If a technical term has no approved Kannada equivalent, flag it for the reviewer rather than inventing a translation. Do not infer a refund, delivery promise or exception from a polite tone. An unresolved policy question remains unresolved in either language.

A customer-reply prompt you can adapt

Replace the input descriptions with the material you are authorized to use. If a required source is missing, obtain it before requesting the customer-facing draft.

Draft a customer-service reply in Kannada using the customer question, current policy and approved glossary I supply. If the question or policy is missing, ask for it before drafting. Use the polite, professional register appropriate to the audience I specify. Preserve names, product names, order identifiers, numbers, amounts, units and dates exactly as supplied unless I authorize a change. Follow the glossary; flag a technical term without an approved equivalent. Do not invent refunds, delivery promises or policy exceptions. Return the Kannada draft, followed by a separate English review note linking each commitment to the supporting source passage and listing missing facts. Keep that review note out of the customer-facing text. Do not send the reply. Ask a fluent Kannada reviewer to check meaning, register and terminology before use.

Check the copied text and the meaning

Use Unicode Kannada text rather than an image of the wording. After copying the draft into its destination, check that the script displays correctly and that characters or spacing have not been lost. Unicode defines the Kannada character repertoire; it does not assess whether a translation is natural or correct.

Have a fluent Kannada reader compare the reply with the original question and policy. Review respectfulness and register, the glossary, names, numbers and each promised action. An English back-translation may expose a discrepancy, but it does not replace this human review.

Source: Unicode: Kannada character chart

Language support is a starting point

Results depend on the selected model, its current capabilities and the evidence you provide. This guide reports no native-speaker assessment or measured Kannada accuracy. Use qualified review when a mistranslation could change a customer commitment.

Prompeteer prepares the instruction. ChatGPT or another destination runs it under that product’s own access rules and limits. Preparing a prompt does not connect to your inbox or authorize sending a reply.