Voice Calendar Help

Tell'endar Help

"Settings" - opens app settings menu
"Help" - opens this help dialogue text

CALENDAR INPUT: (All Optional)
Month(s), by name spoken, "January, February, March…"
Date(s), by numeral, spoken, "first, second, third…", or 'tomorrow'
Day(s), by name spoken, "Monday, Tuesday, next Wednesday…" even, "third Thursday of May"
Year(s), by digit, spoken, "two-thousand fifteen.." or similar.
Time(s), by hour, minute, specified time of day, and general (noon/midnight)
In addition, "one twelve" is interpreted as January 12th or December 1st based on user preference
Stating, "one twelve fifteen" is interpreted as that preference plus year, 2015

If input contains, 'all day' - then 'all day status' Calendar event(s) created for the day(s) specified.

If input contains, 'busy' or 'unavailable' - then the event(s) created are marked as 'busy' in calendar(s).

If no date or time is specified - entry created today, single event, lasting from midnight morning to midnight that night.

If beginning time is specified, but no end time - entry will begin at time specified and end at midnight that day.

If no year date is specified, and the requested month falls behind the current month - then the event will start on that month and day for the following year, not the current one.
For example: it is December and the request is for January. The event would be added for January next year, not the current year in January, which would be in the past.
The exception is when a year is specified. Then even if it happened in the past, the event will be entered for the year specified.

Stating an event by date, i.e. the 1st, 2nd, 3rd, etc without specifying a month will insert an event in the same month for any days that exceed the current day and in the following month for days falling behind the current day.
For example: it is January 8th, and input is, "On the 12th and 4th…", an event will be created for January 12th and February 4th.
The exception is when a month is specified. Then all requested event dates will apply to that month only.
In the same example, specifying January anywhere in the input would input an event for both days in January, regardless.

Stating an event by day, i.e. on Monday, Tuesday, next Wednesday, etc without specifying a month will insert an event in the current week for any days that exceed the current day and in the following week for days falling behind the current day.
For example: it is Thursday, and input is, "On Saturday, Monday, and next Sunday…", an event will be created for Saturday the same week and Monday and Sunday the following week.
In the example above, specifying Thursday would create an event for Thursday next week, not the current day since no specification is required for an event entry in the current day.
The exception is when a month is specified. Then a numerical specification of day in month takes precedence over a specification by day.
The exception to this precedence when a month is specified is when the day itself is quantified i.e. "the 4th Friday in May"

It is not possible to specify multiple months in a single voice command

All Calendar events will end the same day they start, EXCEPT; events using hours and/or minutes to specify end time.
For example: instead of saying an event lasts from 4 p.m. to 4 a.m., a user would state the event begins at 4 p.m. for 12 hours.
Otherwise, the entry made will not work exactly.

The application can determine a desired start or end reference time provided a frame of reference. For example, "from ten to four" does not provide reference. However, "from ten am to four", or "from ten to four pm" contain valid frame of reference to determine desired unspecified start or end times.

Experimental Commands:
These commands search 'all' calendars on a device for an event. Otherwise the function of the commands would be eliminated. As result, these commands can take time to process.

Example, "Am I available…?"
Example, "Am I busy…?"
Result is an audio notification of availability for time specified.

Example, "What am I doing…?"
Example, "What is scheduled for…?"
Result is a visual display of event titles for time specified accompanied by an audio announcement.
Note: Audio playback can be muted by long-pressing the 'exit' (red arrow) button
Note: To only hear audio playback, user can specify, "no display". As in, "do not display events", or "no results displayed".


Voice Input Timeout
Alters time the voice input prompt remains active until a word is recognized

Append Voice Edit Screen
Allows user preview and editing of recognized voice
The timeout setting applies only when idle and not while editing

The following actions are available:

  • Edit - manually via text input
  • Add - append additional voice recognition to the current recognition note: if recognition fails or process crashes user will return to input edit screen with last specified value
  • Test - run a simulation of app results for event entry creation note: functions; Add, Reset, Submit, and Exit are available after performing a test. Special note: an invalid event recognition will produce test results, but if submitted with errors will result in clearing and restarting voice recognition
  • Submit - process input through application
  • Exit - exit application note: when testing 'exit' returns to input edit screen

Calendar Manual Entry Screen
Allows user to add description and location to created event
The timeout default action is Submit and time is based on Append Voice Timeout if set. Else, the default time used is 5 seconds

This is displayed after the resulting event calculations and the following actions are available:

  • Submit - create the entry with displayed values note: long-press 'Submit' to 'Share' an event
  • Reset - erase current voice input and completely start over
  • Obtain Current Address (icon in location field) - uses a devices GPS to determine location coordinates, which results in a determined street address for the user and auto-fills the field with the determined value note: GPS can be inaccurate indoors, as result a user notice appears next to the location field title indicating the current radius of accuracy Special note: long pressing the icon terminates the Obtain Current Address function if taking too long, the function will terminate itself if no location can be determined in 2 minutes. The user will be notified of any resulting errors in the location field.
  • Retry Event Entry Recognition - if for some reason the Event start or end is recognized correctly, but not calculated correctly (often by a fixed offset in minutes to the next hour) that means unfortunately the device did not return a value for the current time in minutes (android bug - reproducible on some devices in the first thirty seconds on the 27 minute mark of the hour) but if you should experience this at any time and notice the event start or end doesn't match what you want long press the header or footer and the app will retry event entry and end calculations for the current input.

Append Voice Edit Default Action
Run a desired action after a specified Idle Input Editing Timeout is reached

Default Share Method

  • None Set/Disabled - User will be prompted for desired share method when function is accessed
  • SMS - Share method always SMS. User share method prompt disabled
  • email - Share method always email. User share method prompt disabled


Use Set Default End Time
Set a desired default end time (in minutes) that an event entry will end, only applies if an event start time is set

Edit Calendar Titles
Set to automatically remove input date(s) & time(s) for a concise calendar entry

Updated Version Check
Long-press the Version ID displayed in settings to check for available application update

Change Logs


Developer of Tasker

Jeremy Harris
Dedicated Beta-tester
For your tireless testing efforts that have identified numerous issues within the application and discrepancies across various platforms. Thank you always for your time and communication.

Nooper Dad
For reminding me, "we colonials" in America recognize date and month backwards from a majority of the world
Thank you sir ;-)

Robert (Bob) Hanson
For providing an example use of an undocumented code character, that turned out to be essential to the apps time recognition feature

The above individuals have contributed with such significant effort, they deserve special recognition and my personal gratitude. The developer would like to acknowledge that without the contributions from these individuals the application would not perform as well as it does for so many users and devices.


  • Multiple start times for an event in a day
  • Multiple months specified at input
  • End time in addition to a specification by hour and/or minute event ending

In the event an entry error occurs, the app will retry voice recognition automatically

Specified minutes to start.
For example: it is 9:51am, an event starts at 11am. If you said, "the 'event' starts in 1 hour and 9 minutes," the process will only recognize input of the hour timeframe, and not the minutes. Actually, the minutes would be recognized, but added to the end time for the event in error. It is the only limitation of the app. In this example, to start at 11am a user would say, "at eleven a.m.".

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License