Draft a welcome message for [RECIPIENT TYPE] who needs to use FileZilla to access [SERVER OR PROJECT PURPOSE]. The access method and setup facts are [CONNECTION DETAILS], the files and workflow are [FILE WORKFLOW], and the required security rules are [SECURITY REQUIREMENTS]. Send it through [CHANNEL] in a [TONE] voice. Write only from the facts I provide. Do not include passwords, private keys, full credentials, or sensitive server details in the message. If credentials must be delivered separately, state the approved delivery method in neutral language. Use “SFTP” only if I specify SFTP; do not incorrectly call FTP, FTPS, and SFTP interchangeable. Produce: 1. A ready-to-send welcome message of 150 to 250 words. 2. A compact setup checklist with the exact fields the recipient must enter in FileZilla, using placeholders for any secret field. 3. A file-handling section covering the correct remote folder, naming convention, upload or download rules, and how to tell when a transfer completed. 4. A support and access section stating the contact route, what diagnostic information to send, and the next action requested from the recipient. Explain common user-visible issues only when relevant: host-key verification on first connection, passive-mode or firewall restrictions, permission denied, incorrect remote path, and incomplete transfers. Do not promise that a connection is secure, compliant, backed up, or monitored unless I supplied that fact. Do not ask the recipient to email passwords or attach private keys. Before answering, self-check that it contains no secret credential material and that each instruction matches the stated protocol and workflow. If a necessary fact such as host, port, protocol, remote path, or support contact is missing, ask up to three clarifying questions before drafting.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [RECIPIENT TYPE] | Describe who is receiving access, such as a client, contractor, or internal teammate. | A freelance video editor |
| [SERVER OR PROJECT PURPOSE] | State why they need access and what system or project it supports. | Upload final social clips for the Northside Dental campaign |
| [CONNECTION DETAILS] | Provide the approved protocol, host, port, username format, authentication method, and any non-secret setup facts. | SFTP; host uploads.example.net; port 22; username supplied in the project portal; SSH key supplied through 1Password |
| [FILE WORKFLOW] | Describe the remote folder, allowed file types, naming rules, transfer direction, and completion check. | Upload MP4 files to /incoming/northside-dental; use client_campaign_YYYY-MM-DD_v01.mp4; do not delete source files; confirm the transfer queue shows Successful transfers |
| [SECURITY REQUIREMENTS] | List access controls, credential-delivery method, retention rules, and restrictions that apply. | Do not share access; do not email keys; use the project portal for access delivery; access expires after the campaign |
| [CHANNEL] | State whether this will be sent by email, ticket, chat, or another channel. | |
| [TONE] | Describe the required tone, such as concise technical, client-friendly, or formal. | Clear and client-friendly |
How to use
- Paste the exact protocol and non-secret connection fields from the administrator or hosting panel.
- Confirm the remote path and naming convention with the person who owns the file workflow before sending.
- Keep passwords and private keys out of the draft; use your approved password manager or portal instead.
- Follow up with: “Rewrite this as a 90-word reminder for a contractor who has not completed setup.”
Variations
SFTP setup email
Use this when a new collaborator needs first-time access instructions.
Write a first-time SFTP setup email for [RECIPIENT] using FileZilla. Approved non-secret settings are [HOST, PORT, USERNAME FORMAT, AUTH METHOD]. The target folder and transfer rules are [WORKFLOW]. Credentials arrive through [SECURE DELIVERY METHOD]. Include a short first-connection checklist and a request to confirm a successful test upload. Do not include passwords, private keys, or unsupported security claims. Flag any missing protocol, path, or support contact before writing.
Transfer failure reply
Use this after someone reports a connection or upload problem.
Draft a support reply to [RECIPIENT] about this FileZilla issue: [ERROR OR SYMPTOM]. Their approved connection type is [PROTOCOL AND SETTINGS], and the relevant workflow is [WORKFLOW]. Give a numbered troubleshooting sequence that starts with safe checks: protocol, host, port, username, remote path, network restriction, and transfer queue. Ask for the exact error text and timestamp if needed. Never request a password, private key, or screenshot containing credentials.
Client upload portal note
Use this when clients only need a short upload instruction, not full technical onboarding.
Write a short [CHANNEL] message for [CLIENT TYPE] explaining how to upload [FILES] through FileZilla. Use these non-secret facts: [CONNECTION FACTS]. The destination and naming rule are [DESTINATION RULES]. Keep the message under [WORD COUNT] words, state how they will receive credentials securely, and give one support contact route. Avoid technical detail that is unnecessary for this audience, and do not include secrets or promise compliance or backup status.
Tips
- Confirm the protocol first: SFTP uses SSH, while FTP and FTPS use different connection and security settings.
- Give recipients one exact remote folder and one filename pattern; vague instructions create misplaced uploads and overwritten versions.
- Ask them to verify a transfer in FileZilla’s Successful transfers tab, not merely that a progress bar reached the end.
- Treat logs, screenshots, passwords, private keys, and full server details as sensitive when collecting support information.
FAQ
Should I put FTP credentials in the welcome email?
No. Use the organization’s approved password manager, portal, or separate secure channel, and tell the recipient where to find them.
What information does someone need for FileZilla?
They normally need the protocol, host, port, username, authentication method, and the correct remote folder. The authentication secret should be delivered separately.
Can one welcome message cover FTP and SFTP?
Only if you clearly separate the settings. Do not tell recipients that the protocols are interchangeable.