Рекомендация: Visit the official 웹사이트 Support 페이지 and submit your inquiry using the typeform form on the 페이지에, which routes directly to the 지원팀에. This channel lets you 제공하기 필요한 details, receive a ticket number, and get a reply within 24 hours.
For live support, request a zoom은 session by choosing Schedule a meeting on the same page. The 프로세스 uses 도구에서 links to connect quickly, and you can 임베드할 the meeting invitation into your own workflow to notify teammates.
Privacy and consent: Our gdpr-compliant workflow follows 제25조 guidance on data protection by design. You may 자발적으로 provide consent for processing, and the 요청 data will be 처리하고 stored only as long as necessary to resolve the inquiry. Access is restricted to the 지원팀에 and security controls apply to stored records.
To improve the 서비스에, run usertesting and compare results with prodeepl translations. Attach the feedback to the 서비스에 ticket to help the team implement improvements. The status and replies appear on the 페이지에, and the 지원팀에 can provide updates as soon as they are available. If you need to share resources publicly, use the 도구에서 임베드된 forms and 연결하여 external sites while keeping 불필요한 data minimized.
마지막으로, keep a copy of your ticket number and monitor updates on the 페이지에; this keeps 커뮤니케이션 clear and ensures you reach a helpful resolution with the support team.
Find the Official DeepL Support Page
Visit the official DeepL site and click Support in the header to reach the primary hub. This 웹사이트가 hosts articles, FAQs, and direct 연락 options. To verify you’re on the official page, check the URL, branding, and the 페이지에 language selector. On this page, zendesk의 ticketing system handles communications for 이용자는, routing questions and 기록하고 keeping a complete history. In 서비스에서 inquiries are categorized and tracked, so 사용자와 agents stay aligned. If you need live help, use 이메일을 to reach an agent and review 이용약관에 for policy details; 사용자와 DeepL share data only as necessary and 따라서만 used for support. We follow합니다gdpr compliance; 개인정보가 protected, 데이터도 encrypted in transit, and 콘텐츠와 개인정보의 flows are described in the policy. The prodeepl ecosystem is described here, including 임베드할 content guidance and the 이용약관을 for developers. For billing or 업그레이드, the page notes usa에 data handling, how to 관리하고 stripe 는 and google are used for payments and analytics. It covers events (이벤트를) and 웨비나에 registrations, and states that data 삭제됩니다 after processing. Use this page as your starting point for clear 커뮤니케이션 and to ensure you 이용자에게 stay on the official page for any inquiry.
How to verify you are on the official page
Check the header branding on web pages and 웹사이트가 domain aligns with DeepL. Look for a clearly labeled Support link, and confirm the 페이지에 contains 이용약관에 and privacy notices. The page should show the Zendesk-based ticketing flow, so 이용자에게 the option to Submit a request appears, and there is a visible 이메일을 path for quick contact. Confirm that 이용자와 DeepL policy snippets are present, and that 따라서만 policy-based actions are shown. If you see unfamiliar domains or suspicious popups, back out and return to the official page to avoid sharing 개인정보의 outside approved channels.
What you can do on this page
Search knowledge articles, open a support ticket, or request a callback. Review 업그레이드 options and 이용약관을 for practical guidance. Manage 개인정보의 preferences, opt into 커뮤니케이션 settings, and track your ticket status across devices. The page explains gdpr and usa data considerations, how 개인정보가 protected, 데이터도 encrypted, and 콘텐츠와 데이터 흐름 is explained. prodeepl context appears for developers who plan to 임베드할 content and use approved integrations with 이용약관을. For subscriptions, the page details usa에 data handling, how to 관리하고, and how stripe는 and google services support payments and analytics. The section on 이벤트를 and 웨비나에 outlines registration steps and retention rules, noting that 삭제됩니다 after completion. Use the official page to stay informed, preserve your privacy, and keep 커뮤니케이션 consistent with DeepL policies.
Select the Best Channel: Help Center, Email, or Live Chat
Choose Live Chat for immediate help; Use Help Center for quick self-service guidance in the 웹사이트의 knowledge base; Email for complex or privacy-sensitive inquiries.
Channel Guidance
우리의 지원하는 시스템에 따라 세 채널이 연결됩니다. Live Chat delivers real-time assistance on the platform에서, and conversations are archived in zendesk for tracking. Help Center offers 기술문서 and 웹사이트의 FAQ; 설문조사를 통해 사용자 의견이 반영되어 캠페인의 콘텐츠가 개선됩니다. 웨비나의 세션은 추가 맥락을 제공하며, 웨비나를 통해 질문에 대한 답을 즉시 얻을 수 있습니다. Email은 민감한 이슈나 긴 문의에 적합하며 usa에 데이터 센터를 활용하여 요청을 처리합니다. 모든 데이터는 protected으로 암호화되며, cloudflare는 네트워크 보안을 강화합니다. qualtrics의 설문조사 도구가 제공되며 데이터의 근거합니다.
Data Handling & Privacy
데이터의 저장과 파기는 정책에 따라 이행하기로 되어 있습니다. 요청은 저장하고 필요 시 파기합니다, 처리됩니다의 타임라인은 채널별로 다르며, townsend 캠페인의 피드백은 제공됩니다.
| Channel | Best For | What to Expect | Data Handling |
|---|---|---|---|
| Help Center | Self-service, quick fixes | 웹사이트의 기술문서, FAQ, and step-by-step guides; 설문조사 데이터는 캠페인의 개선에 반영됩니다. 웨비나의 Q&A를 참고할 수 있습니다. | 데이터의 처리는 정책에 따라 진행됩니다; 저장하고 필요 시 파기합니다; protected으로 암호화되며 cloudflare는 보안 레이어를 제공합니다. qualtrics의 피드백 도구가 제공됩니다. |
| Complex issues, privacy-sensitive requests | Written 기록으로 남고, 처리됩니다 within 24–48시간 범위; usa에 데이터 센터 활용으로 라우팅됩니다. | 데이터의 저장 및 관리가 이루어지며, 웨비나를 통한 기록도 이행하기에 참고됩니다. townsend 캠페인의 정보가 포함될 수 있습니다; qualified로 검토됩니다. | |
| Live Chat | Urgent questions, quick resolutions | 실시간 대화로 즉시 답변; 현황은 zendesk에 연계되어 해당 참여자의 이력과 함께 처리됩니다. 웨비나를 통한 보충 정보도 제공됩니다. | 데이터는 플랫폼에서 실시간으로 처리됩니다; protected으로 관리되며, cloudflare는 접속 보안을 유지합니다; voice의 기능도 활용됩니다. |
Prepare Your Request: Account Details, Email, and License
Prepare your request with three essentials: account ID, registered email, and the license key. Attach the exact license type and the organization name so the support team can locate your records quickly. If you run usertesting은, this helps link testing data to your account; 처리되는 데이터 흐름은 근거합니다 for compliance. 체결하려면, include any contract IDs if you expect a formal agreement to be signed.
Account details: Provide region and country (usa에) if applicable, and the primary contact (지원자의) name and role. If a specific 대상으로 signer must sign, include their contact and the contract ID to route the ticket correctly.
Email and license: Use a verified email that matches the account records, and include the license status and renewal date. If needed, reference the usa에 address; 보장합니다 that communications stay secure and comply with 이용약관을. 데이터는 사용되며 보안 기준으로 처리됩니다; 유지하고 기록을 최신 상태로 관리합니다.
Privacy and data handling: Explain how 개인정보는 protected and processed; indicate whether data 전송합니다 to vendors and whether it is 일시적으로 stored 기반으로 on the support objective. Access is limited to 이용자를, and we enforce the principle of least privilege. If your team is in francisco, specify the 지원팀에 contact and we 따릅니다 internal SLA and privacy controls; 발생하지 in regular operation means we fix issues quickly; 서비스는 포함됩니다 in standard packages; house 개선하는 보안 절차를 유지합니다.
Submission channels and tools: Use typeform은 to collect intake details, or qualtrics for advanced surveys. stripe는 license payments를 처리합니다. Include a linkedin profile for identity verification if applicable. For live sessions, you can invite participants to 웨비나에, and hotjar의 설문조사를 참조해 context; 전송합니다 to the assigned agent. We 보호하기 of your data and follow the 이용약관을; for any format needs, consult the 지원팀에 to adapt; 따릅니다 privacy policies and governance guidelines. 서비스는 포함됩니다 in standard plans.
Submit a Translation Correction or Feedback with Clear Examples
Provide your translation correction with the original 텍스트의, your proposed translation, and a concise justification. Use typeform to submit on the 페이지에 Support portal and attach two concrete examples that illustrate the issue.
Structure each example with its context: where the phrase appears, the source nuance, and how your version improves clarity. Include the exact sentence, the proposed text, and a brief rationale. Include the 텍스트의 surrounding sentences to show impact.
Data handling: Corrections and metadata are stored in the 데이터베이스에 and linked to the relevant content segment. We use Salesforce (salesforce, salesforcecom) to track user submissions, and we may share limited data 사이에서 하청업체와 internal teams to implement the update. If authentication is needed, linkedin은 can be used to verify contributors.
Privacy and retention: We minimize 개인정보의 exposure in the submission, 확인하고 저장하며 보호하는 data, and we 삭제합니다 after retention per 제25조 처리방침. Access is restricted to authorized personnel, and we conduct regular audits to ensure compliance.
Hotjar and usability: hotjar는 used to study how corrections are submitted and navigated. hotjar의 data is anonymized, stored securely, and not used to reveal personal text. We use it solely to improve the submission flow and the overall experience for users.
Review steps: A reviewer checks the correction for clarity and accuracy, then updates the translation corpus in the system. The change appears on the 페이지에, and you receive a confirmation email with the details. If you want deeper discussion, we offer a 웨비나를 for a live walkthrough of the update process.
Sample submission format (for clarity): Original: "Hello world." Propuesta: "Hello, world." Rationale: The comma improves English rhythm in UI copy. 텍스트의 surrounding context helps ensure consistency across harcourt datasets and across related texts. Include additional examples as needed to demonstrate consistency with 데이터베이스에.
We value your input and strive to keep the service와 translation quality high. 바랍니다 to share precise, actionable corrections. If you need help, join a 웨비나에 and learn how to craft strong corrections, and we will provide updates across 데이터베이스에 and related systems like salesforce, ensuring your feedback is processed efficiently and securely, 감사합니다.
Request API or Pro Plan Help: What to Include
Provide a focused API or Pro Plan request with a clear goal and measurable outcome. Include the exact API endpoint or Pro feature you need, the language pairs, and the expected throughput. For context, describe the 캠페인의 scope, the 클라우드 environment you will use, and how you 파악하여 current usage, limits, and data residency requirements. Reference your 처리방침 and 이용약관에 to ensure alignment with policy, and add a link to the 웹사이트 where the terms apply. If you plan to 체결하려면 contract, mention it in the request. Also include costello as a project or data source to help specificity.
Be explicit about data flow: indicate that 메타데이터에만 is stored, while translation data may reside in 데이터베이스에 for analytics, and that content processed in deepl에서 is routed through the API with the proper safeguards. State that 처리됩니다 under the terms of your 정책, and that 전송되지 beyond your 네트워크 without explicit consent. Specify retention periods, deletion schedules (애플리케이션이하 components included), and how 삭제합니다 will be triggered. Include a page reference (페이지에) to where these rules appear. If you use cloud services, mention how they integrate with your policy and indicate any constraints related to processing within the 플랫폼에.
Attach references to zendesk conversations, the 기술문서 that documents the API behavior, and a gitbook page you use for onboarding. If you rely on hotjar on your 웹사이트, note that you provide a sanitized data set for debugging, and 제안된 설정을 제공하고 공유합니다. Include 보내주시기 the Zendesk ticket ID and links to the 웹사이트, 기술문서, and the gitbook page so the team can reproduce and track the integration. Prodeepl features 포함됩니다 in the plan, and Cloudflare는 보장하기 security and performance. Where applicable, provide references to cloud-based services you use and how they are 기록하고 모니터링되는지, ensuring you meet your 측정 기준 across 네트워크 and platform layers.
What to Include: Checklist
API endpoint, Pro plan name, estimated monthly volume, data flow diagrams, compliance notes (이용약관에, 처리방침), sample payloads, data retention, deletion rules, and links to 메타데이터에만, 데이터베이스에, and deepl에서 processing. Include references to zendesk conversations, 기술문서, hotjar configurations, and the gitbook page that documents the deployment. Confirm that prodeepl features are included in the quote and detailing how cloudflare는 보장하기 security and performance. Indicate how the 서비스는 platform에 통합되며, what 네트워크 기록하고 선택하면 알림 채널을 통해 업데이트를 받는지.
Track Your Ticket: Status Updates and Timelines
Enable real-time updates now: open your ticket in the support portal, and turn on Notifications to receive alerts via the portal or supportatdeeplcom으로.
- Timeline literacy: The ticket view shows stages such as Received, Assigned, In Progress, Awaiting Customer, Pending External Input, Resolved, and Closed. This helps 이용자 track progress at a glance; 전송합니다 updates appear 도구에서 the 대상으로 you watch the dashboard.
- Speeding up a review: Attach pptx files and reference documents (roda) to provide context; this 프로세스 helps reviewers reach decisions faster. For billing questions, stripe references may appear on the ticket when applicable.
- Cadence and expectations: Initial replies for critical issues are typically within 4 hours; standard inquiries are usually answered within 24 hours. Updates are 정기적으로 posted during business hours; if there is no activity for 48 hours, 방지하기 missed updates by escalating via supportatdeeplcom으로.
- Engagement and feedback: Use the ticket comments to clarify requirements, and share 설문조사에 links or attach 설문조사 after resolution. 여기에서 you can access the 설문조사 and leave feedback to improve the service, and 이용자에게 ongoing updates stay aligned with your needs.
- Privacy and retention: 웹사이트가 제공하는 개인정보보호 measures apply, and we comply with gdpr and 이용약관에. We 파기합니다 older logs and personal data 정기적으로 according to retention policy.
- Resources and channels: We publish guides on gitbook and offer free resources 바탕으로 your workflows; 사용합니다 to speed up onboarding. linkedin은 소식 채널로도 사용되며, 방문하거나 공지 및 업데이트를 확인할 수 있습니다. We also use tools like ethnio to collect quick feedback.
- Survey participation: 설문조사에 참여하면 서비스 품질 개선에 반영됩니다. 설문조사는 여기에서 접근 가능합니다; 참여해주신다면 향후 응답 시간이 단축될 수 있습니다. 방문하거나 관련 페이지로 이동해 참여하십시오.
- Escalation path: If you need faster attention, contact supportatdeeplcom으로 with your ticket ID, screenshots, and any attachments (pptx). We will acknowledge and adjust timelines accordingly.
Get a Faster Reply: Pro Tips for Clear Communication
Provide a single-line summary at the top: "DeepL Translate: upload fails with error 500." Include your account ID, the exact error text, and a single file (pptx preferred) showing steps to reproduce. Route the ticket via zendesk by selecting the correct category and priority, then attach a concise log or screenshot. Reference the exact URL or app path (텍스트의) and include 메타데이터: device, 브라우저와 OS version, and locale. List the steps to reproduce in a numbered block, and keep the body tight to minimize back-and-forth. Clarify 수집하기 of data and declare how 개인정보는 will be treated, using 제25조 and 제3국에 rules; if possible, use 가명정보를. If you operate in USA에 or japan regions, note the regional SLA and business hours to set expectations. If you plan a 웨비나에 or screen sharing (zoom이), mention it in the ticket and attach invites as separate files, never paste full logs in the body. Use the same ticket thread (zendesk의) for updates, and avoid parallel messages that slow the process. 보장하기 the message clarity by including a short, direct bullet list of what you did and what remains unresolved. This approach keeps the conversation on the house path to resolution, on the road to a faster reply.
Pro Tips for Clear, Actionable Messages
Keep phrases tight: subject line, issue summary, and desired outcome in the first two lines. Attach only one file (pptx or PDF) that shows the steps to reproduce. Use metadata fields to capture device, 브라우저와 OS version, and timezone. For privacy, explicitly state whether you 수집하기 data and how 개인정보는 will be processed in 제25조 and 제3국에; mark 가명정보를 when sharing. When referencing multiple components, mention product name and version and the specific page number (페이지에) if relevant. If the issue touches a service, note the platform에 and any related services like 설문조사, 텍스트의 elements, or road-related implications. If you mention Zoom, provide a single Zoom이 link and the date of the 웨비나에 session. Always use zendesk's ticketing to keep everything in one thread (zendesk의).
Ready-to-Use Templates
Subject: DeepL issue #
