[sims] So I saw InTouch Today...

[CAM]

I have to confess, I was quite impressed with what it can do. The ability to send automatic messages to staff members and the possibility of using it to send reports home were definate attention grabbers for me. What do people on here make of InTouch?

 

Also does anyone know if it is possible to send messages home for the contacts of students in a particular subject instead of the students?

[siuko]

I do not have much info for InTouch as I don't use it regularly but the one thing I can say is on our setup its is very Slooooooooooooooooooooooooooow to open the UI etc

[vyperz]

we found it expensive compared to schoolcomms and teachers2parents

[TechMonkey]

Used it at previous place. As you said, very powerful what it can do but as siuko said, it can be very slow. Admin staff found it better (but slow) to use than other mailers we had used and easier to manage by virtue of using data you all ready have.

[PhilNeal]

If your server is at our minimum recommended standard, InTouch should not affect performance. If it does please raise a case.

[siuko]

If your server is at our minimum recommended standard, InTouch should not affect performance. If it does please raise a case.

 

Hi Phil - it doesn't affect the performance of anything else - it is just the InTouch Window / UI itself is just very slow to load and navigate through.

 

Is this not standard behavior? Should I still raise a ticket?

[PhilNeal]

@siuko The first time its called it will hesitate but thereafter it should be fine. I've seen lots of demos and not seen any performance issues. Do raise a ticket if it seems to slow.

[mattianuk]

Have ordered it, awaiting someone to actually deliver and install it now - only been 2 weeks :S

[IrritableTech]

It's pretty good. We decided to use it because it was so integrated into sims.net. There is a pause (definitely first time, possibly more often [sorry Phil]) opening it up, but we can live with it.

 

We do have an issue every 6-8 weeks where one of the services wont communicate with capita any more. We've had it today, but after restarting IIS, OpenVPN and pinging the capita servers everything comes to life again. I think it's a routing issue as a result - which I need to look into again.