manually send reminder #1234

Open
nerdoc opened this Issue Jan 1, 2017 · 11 comments

Projects

None yet

6 participants

@nerdoc
Contributor
nerdoc commented Jan 1, 2017

Happy New Year altogether!

This is not a bug, but more a wish/feature request.
When automatic reminders are NOT configured, it should be possible to send a reminder manually.

The use case for this is - I don't want automatic reminders because sometimes I need to have more time to check my bank accounts - and if IN sends automatic reminderstoo often, the clients will get angry ;-)

So what I would suggest is add an item "send reminder" into the button "more actions" on the invoices/%/edit page - IF the invoice is over due. Don't show this menu item when there a reminder is not adaequate = within due.

Problem to solve: If "automatic reminders" are disabled, you cannot customize the reminder text - which is necessary for manual reminders.
So maybe this could be changed this way:

  • Let the user choose between auto reminder/manual reminder
  • Let the user edit the text templates for the reminders in any case (manual/auto reminder)
  • When set to auto reminder, let the user choose the Schedule, when manual, set Schedule inputs to disabled (or hide them)

Mockup:
bildschirmfoto vom 2017-01-01 15-06-17

@realtarget

Nice idea but i would suggest to place an additional button in the invoice view which sends a reminder based on the stage of the overdue process (first text, second text, third text) and increases the dunning level.

Mockup:

invoiceninja_send_reminder

@Braintelligence

Basing it on the stage of the overdue process is a bad idea IMO.
Normally you want the reminder mails to be based on one another. If I send the second reminder mail as the first one (because it took me so long to send the reminder mail) it will probably contain something like "Since you didn't react to the first reminder..." which would be wrong.

The way to go for this should be to manually remind the user (perhaps via mail as well) and allow him to send the first reminder mail whenever, and then start the next countdown with the next reminder, I think.

@nerdoc
Contributor
nerdoc commented Jan 2, 2017 edited

@Braintelligence that sounds really good to me.
[ Send reminder ($number) ]
as Button. (I am too lazy creating a mockup ATM)
or
[ Send first reminder ]
(and counting second, third...)

@realtarget

@Braintelligence I did not mean the overdue process but the stages of reminding. So the user can manually choose when to send the first reminder (eg. 10 days after the due date for customer A and 20 days for Customer B). The reminders go one step further after sending.

First click after x days: Friendly reminder
Second click after y days: Warning
Third click after z days: Brutal Warning ;-)

@konstantinrudi

๐Ÿ’ฏ

@hillelcoren
Member
hillelcoren commented Feb 5, 2017 edited

Here's what we're working on:

  • The template select enables you to choose between the initial email and the reminders and will be automatically set based on the history
  • The customize tab contains the same editor as on /settings/templates_and_reminders
  • The history tab has a table showing the past times the invoice was emailed [template|contact|date]

email

@nerdoc
Contributor
nerdoc commented Feb 5, 2017

Great!

@Braintelligence

Do I understand correctly that we can customize the mailing for every invoice uniquely with this?

@hillelcoren
Member

That is correct

@Braintelligence

Nifty ๐Ÿ˜ธ

@hillelcoren
Member

Thanks for everyone's input, it was a big help working out the UI.

@hillelcoren hillelcoren added a commit that referenced this issue Feb 5, 2017
@hillelcoren hillelcoren Working on #1234 80ccd4f
@hillelcoren hillelcoren added a commit that referenced this issue Feb 5, 2017
@hillelcoren hillelcoren Working on #1234 30045ec
@hillelcoren hillelcoren added a commit that referenced this issue Feb 5, 2017
@hillelcoren hillelcoren Working on #1234 ce49bf3
@hillelcoren hillelcoren added a commit that referenced this issue Feb 6, 2017
@hillelcoren hillelcoren Working on #1234 58c50ed
@hillelcoren hillelcoren added a commit that referenced this issue Feb 6, 2017
@hillelcoren hillelcoren Working on #1234 865c379
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment