The complete setup path · Part 7 of 7

Get Help with SMTasker: Getting Started Part 7

If a device will not connect or a campaign behaves differently from expected, clear details help support investigate faster. The final Getting Started video shows the available support path and how to report an issue with useful context.

▶ 9:13 videoPublished July 15, 2026

Prefer YouTube? Watch the original video

BEFORE YOU PRESS PLAY

Get set for this lesson

Open the dashboard and identify the exact device, social account, and automation involved in your issue. The support form becomes much more useful when you can show both what you expected and what happened.

FOLLOW THE WALKTHROUGH

What happens in the video

Find Contact Support

The recording points to the headphones icon in the dashboard’s upper-right area. The Contact Support form pre-fills Reply To with the account email, which helps associate the request with the correct workspace. It also offers a category such as Payment, Bugs, Features, or Other.

Describe a reproducible issue

The presenter fills the Message field with the platform, device, account, intended action, exact clicks or settings, observed result, and when it began. “My tool does not work” gives little to investigate; an error message and the step where it appeared are much more useful. Avoid including passwords, 2FA secrets, or private API keys.

Capture the relevant screen

A camera control near the dashboard’s lower-left area opens a screenshot flow. The browser requests permission to capture a tab; after you approve it, a preview appears. Crop only if it keeps the context needed to identify the problem. You can download the image for email or add it directly to the support form.

Attach context without losing the error

The video demonstrates stacking screenshots from Settings, Sources, and an error state, with a limit of ten attachments in the form shown. Include the campaign name and device row when useful, but hide credentials or unrelated personal data. Submit the form after reviewing the reply email.

Use email when it fits better

The alternative shown is contact@smtasker.com. An email can carry the same structured issue description and screenshots. The video encourages detailed reports; it does not establish a guaranteed resolution time for every request.

WATCH FOR THESE DETAILS

Check this as you follow along

  • Keep the Reply To address accessible for the response.
  • Choose a category that matches the issue, then include the exact error and approximate time.
  • Capture the full browser tab only when the useful information is visible and private data are hidden.
  • Limit attachments to the screens that explain the problem; the form shown accepts up to ten.
  • Never send login passwords, 2FA secrets, or full API keys in a ticket.

AFTER WATCHING

Put this into practice

If the issue concerns setup, mention the numbered lesson and the first step that diverged from the video. If it concerns an automation, include its account, source, schedule, status, and Summary or Results entries so support can follow the same path.

RELATED READING

Keep the guide nearby

Open the relevant written resource when you need to check a setting while working in your own dashboard.

Read how to get support

PUT THIS LESSON TO WORK

Ready to try it with SMTasker?

Create your account, connect your Android phone, and follow the setup at your own pace. Your next workflow starts here.